Authentication
Exact credential types, headers, and where each one is used
Authentication
| Credential | Header | Used For |
|---|---|---|
| Provider API key | x-api-key: <provider-api-key> | provider backend calls on api.edge.vrplatform.app |
| Session token | Authorization: Bearer <accessToken> | iframe product API calls on api.edge.vrplatform.app |
| Ingest token | Authorization: M2M <jwt> | raw ingest submission on ingest.edge.vrplatform.app |
Provider API Key
Use the provider API key for backend flows such as:
GET /teamsPOST /teamsGET /appsPOST /connectionsPOST /auth/embed/session
For team-scoped routes, also send:
x-team-id: <managed-team-id>Session Token
POST /auth/embed/session returns the session token used by the iframe.
Use it on product API calls from the embedded frontend.
Ingest Token
Raw ingest is a separate integration contract.
Required scope:
ingest:submit