Ingresse · Authentication Profile

Ingresse Authentication

Authentication

Ingresse secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyTicketingEventsTicketing as a ServicePaymentsEntertainmentEvent ManagementBrazilSDKs
Methods: apiKey Schemes: 1 OAuth flows: API key in: query

Security Schemes

apikey apiKey
· in: query (apikey)

Source

Authentication Profile

ingresse-authentication.yml Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://developer.ingresse.com/docs
docs: https://developer.ingresse.com/docs
summary:
  types: [apiKey]
  api_key_in: [query]
  notes: >-
    Ingresse authenticates requests with an API key passed as the `apikey`
    query parameter (the account's public key). Every API key is individually
    generated by the Ingresse team on request (no self-service provisioning);
    an integration form is required. User-scoped calls additionally carry an
    authenticated user token. Private-key signature details are documented
    behind the developer-portal login and are not captured here.
schemes:
  - name: apikey
    type: apiKey
    in: query
    parameter: apikey
    description: >-
      Account public API key passed as the `apikey` query parameter on every
      request. Issued individually by Ingresse.
    source: https://developer.ingresse.com/docs