Quinyx · Authentication Profile

Quinyx Authentication

Authentication

Quinyx secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

Workforce ManagementSchedulingHuman ResourcesTime TrackingForecastingEmployee EngagementRetailHospitalityCompany
Methods: apiKey, oauth2 Schemes: 2 OAuth flows: clientCredentials API key in: header

Security Schemes

employee_OAuth2ClientCredentials oauth2
· flows: clientCredentials
BearerAuth apiKey
· in: header (Authorization)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: openapi/quinyx-api-v2-openapi.yml, openapi/quinyx-api-v3-openapi.yml, openapi/quinyx-userapi-v2-openapi.yml
docs: https://developer.quinyx.com/api/v3/authentication
notes: >-
  Quinyx API v2/v3 use OAuth 2.0 client-credentials. Obtain Client ID + Client
  Secret from Account Settings > Integration credentials, then POST
  grant_type=client_credentials with the requested scopes to the regional token
  endpoint (https://api.eu.quinyx.com/oauth/v3/token or api.na...). Tokens are
  bearer, expire after ~3600s. The legacy User API (v2) uses a bearer token
  passed in the Authorization header.
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
schemes:
- name: employee_OAuth2ClientCredentials
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: /oauth/v3/token
    scopes: 4
  description: OAuth2 Client Credentials flow. See https://developer.quinyx.com/api/authentication
  sources:
  - openapi/quinyx-api-v2-openapi.yml
  - openapi/quinyx-api-v3-openapi.yml
- name: BearerAuth
  type: apiKey
  in: header
  parameter: Authorization
  sources:
  - openapi/quinyx-userapi-v2-openapi.yml