generated: '2026-09-17'
method: searched
source: https://snap.flyhold.in/docs.html
docs: https://snap.flyhold.in/docs.html
corroboration: >-
  https://snap.flyhold.in/llms.txt states: Auth (any one) — query api_key, or header X-API-Key,
  or Authorization Bearer <key>.
checked: '2026-09-17'
summary:
  types: [apiKey, http]
  api_key_in: [query, header]
  http_schemes: [bearer]
note: >-
  Snap API uses a single opaque API key issued from the dashboard after signup (register.html grants
  200 free credits). The same key may be presented three interchangeable ways. There is no OpenAPI
  securityScheme published; this profile is read from the developer documentation and llms.txt, not
  derived from a machine-readable contract.
schemes:
  - name: api_key_query
    type: apiKey
    in: query
    parameter_name: api_key
    aliases: [token, apiKey]
    description: >-
      Pass the dashboard API key as the api_key query parameter (aliases token / apiKey accepted).
      Convenient for browser and n8n HTTP-node use; note it exposes the key in URLs and logs.
    sources: [docs.html, llms.txt]
  - name: api_key_header
    type: apiKey
    in: header
    parameter_name: X-API-Key
    description: Pass the dashboard API key in the X-API-Key request header. Recommended for server-to-server use.
    sources: [docs.html, llms.txt]
  - name: bearer
    type: http
    scheme: bearer
    description: >-
      Pass the dashboard API key as a bearer token via Authorization: Bearer <key>. Same key value
      as the other two methods.
    sources: [docs.html, llms.txt]
failure:
  status: 403
  meaning: Missing, invalid, or inactive API key.
key_provisioning:
  signup_url: https://snap.flyhold.in/register.html
  free_grant: 200 credits/month on the Developer tier