Beaconstac · Authentication Profile

Beaconstac Authentication

Authentication

Beaconstac secures its APIs with apiKey across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyBig DataQR CodesDigital Business CardsMarketingAnalyticsSaaSProximity
Methods: apiKey Schemes: 2 OAuth flows: API key in: header

Security Schemes

TokenAuth apiKey
· in: header ()
OrganizationId apiKey
· in: header ()

Source

Authentication Profile

beaconstac-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://apidocs.uniqode.com/, https://www.uniqode.com/qr-code-generator/api
docs: https://apidocs.uniqode.com/
# Derived from the published API documentation (no OpenAPI available to mechanically derive).
summary:
  types: [apiKey]
  api_key_in: [header]
  oauth2_flows: []
schemes:
- name: TokenAuth
  type: apiKey
  in: header
  parameter_name: Authorization
  format: "Authorization: Token <API_KEY>"
  description: >-
    A dashboard-issued API key sent as a Token in the Authorization header. Requests also
    require an Organization ID (obtained from the Uniqode dashboard's API section) to scope
    the account. No OAuth2 flow is exposed for the public REST API.
  sources: [https://apidocs.uniqode.com/]
- name: OrganizationId
  type: apiKey
  in: header
  parameter_name: Organization-Id
  description: Organization identifier obtained from the dashboard API section, sent alongside the token.
  sources: [https://www.uniqode.com/qr-code-generator/api]
notes:
- End-user account access to the Uniqode dashboard additionally supports 2FA and SAML-based SSO (Auth0 is the identity subprocessor); these govern dashboard/SSO login, not the REST API token.