Qentaz · Authentication Profile

Qentaz Authentication

Authentication

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

CompanyPaymentsCollectionDisbursementsReconciliationFintechColombiaWebhookFraud PreventionWhatsApp Payments
Methods: apiKey, http Schemes: 4 OAuth flows: API key in: header

Security Schemes

authKeyBearer http
scheme: bearer
accessToken apiKey
· in: header ()
childId apiKey
· in: header ()
webhookSignature apiKey
· in: header ()

Source

Authentication Profile

Raw ↑
generated: '2026-07-20'
method: searched
source: https://docs.qentaz.com/documentation/autenticacion/token
docs: https://docs.qentaz.com/documentation/autenticacion/token
summary:
  types: [apiKey, http]
  model: two-step-bearer
  api_key_in: [header]
  notes: >-
    Two-step bearer authentication. A static, long-lived authentication key
    (auth_key, issued per integration) is sent as an HTTP Bearer credential to
    GET /token, which returns a short-lived access_token (expires_in seconds,
    e.g. 3600). That access_token is then sent on every subsequent request in
    the custom x-auth-token header. No OAuth2/OIDC discovery is published; the
    auth_key is provisioned out of band. Administered ("child") accounts are
    selected with an optional child-id header.
schemes:
- name: authKeyBearer
  type: http
  scheme: bearer
  used_on: GET /token
  header: Authorization
  format: 'Bearer {auth_key}'
  description: >-
    Static per-integration authentication key exchanged for a temporary access
    token. Presented as an HTTP Bearer credential to the token endpoint.
- name: accessToken
  type: apiKey
  in: header
  name_param: x-auth-token
  used_on: all protected endpoints (e.g. POST /transaction, GET /v1/merchant/transaction/)
  description: >-
    Short-lived access token returned by GET /token, sent on every protected
    request. Value is the access_token from the token response.
- name: childId
  type: apiKey
  in: header
  name_param: child-id
  required: false
  description: >-
    Optional business/account selector used with administered (managed / child)
    accounts to scope a request to a sub-account.
- name: webhookSignature
  type: apiKey
  in: header
  name_param: Authorization
  format: 'Bearer base64(client_id:client_secret_key)'
  direction: inbound-to-your-endpoint
  description: >-
    Trazo signs outbound webhook deliveries with a Bearer credential built from
    base64(client_id:client_secret_key) so your endpoint can verify authenticity.
token_endpoint:
  method: GET
  path: /token
  response:
    access_token: string
    expires_in: integer (seconds)

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/qentaz-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.