Avionté BOLD API: authenticate via OAuth2 client_credentials
domain: avionte.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get access to the Avionté BOLD APIs and receive your X-api-key, client_id, client_secret, and scope from Avionté (Step 1 in the developer portal's Getting Started guide).
POST to https://api.avionte.com/authorize/token with header Content-Type: application/x-www-form-urlencoded and header X-api-key set to your provided API key.
In the request body include grant_type=client_credentials, client_id, client_secret, and scope (use avionte.aero.compasintegrationservice for the BOLD Front Office API and Partner Additions API).
Read the access_token, expires_in (default 3600 seconds), and token_type (bearer) fields from the 200 OK JSON response.
Attach the token as an Authorization: Bearer {access_token} header on subsequent Front Office API calls, and refresh it before it expires.
Known gotchas
The token expires after 3600 seconds by default — long-running integrations must refresh proactively rather than relying on a single token for the session.
The scope value must match exactly what Avionté issued for your integration (e.g. avionte.aero.compasintegrationservice); an incorrect scope returns a 400 Bad Request rather than a partial-access token.
The X-api-key header (API Gateway key) is separate from the OAuth client_id/client_secret — both are required together, and mixing them up causes authentication failures.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?