Burner · Authentication Profile

Burner Authentication

Authentication

Burner secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyPhone NumbersSMSMMSVoiceMessagingTelephonyPrivacyCommunicationsSecond Phone NumberOAuthWebhooks

Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

OAuth2 oauth2

· flows: authorizationCode

Source

Authentication Profile

generated: '2026-07-18'
method: searched
source: >-
  https://www.burnerapp.com/llms.txt ;
  https://github.com/adhoclabs/burner-app-starter-kit (src/core/BurnerApi.js, README Authentication section)
summary:
  types: [oauth2]
  api_key_in: []
  oauth2_flows: [authorizationCode]
  token_transport: bearer
notes: >-
  Burner authenticates API access with OAuth 2.0. Third-party apps request Burner
  OAuth app credentials, obtain an access token, and call the API with an
  `Authorization: Bearer <token>` header. The official client also sends an
  `X-Application-Version` header. Derived from the documented developer surface
  (llms.txt) and the first-party Burner App Starter Kit client, which is the
  authoritative reference for the live request shape. No published OpenAPI spec.
schemes:
  - name: OAuth2
    type: oauth2
    flows:
      - flow: authorizationCode
    token_transport: bearer
    header: Authorization
    format: "Bearer <access_token>"
    sources:
      - https://www.burnerapp.com/llms.txt
      - https://github.com/adhoclabs/burner-app-starter-kit
    evidence: >-
      llms.txt: "OAuth 2.0 authentication for API access and third-party
      integrations"; BASK README "Request Burner OAuth app credentials";
      BurnerApi.js sends `Authorization: Bearer ${this.token}`.