Xquik · Authentication Profile

Xquik Api Authentication

Authentication

Xquik secures its APIs with apiKey and http across 3 declared security schemes, as derived from its OpenAPI definitions.

social media dataX / Twittersocial listeningdata extractionautomationwebhooksMCPdeveloper API
Methods: apiKey, http Schemes: 3 OAuth flows: API key in: cookie, header

Security Schemes

apiKey apiKey
· in: header (x-api-key)
oauthBearer http
scheme: bearer
cookieSession apiKey
· in: cookie (__Host-xquik_session)

Source

Authentication Profile

Raw ↑ 
generated: '2026-08-13'
method: derived
source: openapi/xquik-rest-api-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - cookie
  - header
schemes:
- name: apiKey
  type: apiKey
  in: header
  parameter: x-api-key
  description: 'Xquik API key passed through the x-api-key header. Xquik-Api-Key is a vendor-prefixed
    alias. API keys beginning with xq_ can also use Authorization: Bearer.'
  sources:
  - openapi/xquik-rest-api-openapi.yml
- name: oauthBearer
  type: http
  scheme: bearer
  description: 'OAuth 2.1 access token passed through Authorization: Bearer. Values beginning
    with xq_ remain Xquik API-key credentials, not OAuth tokens.'
  sources:
  - openapi/xquik-rest-api-openapi.yml
- name: cookieSession
  type: apiKey
  in: cookie
  parameter: __Host-xquik_session
  description: Secure Xquik browser session cookie.
  sources:
  - openapi/xquik-rest-api-openapi.yml