This article covers CloudAhoy's Organizational-Level APIs. It will discuss organization-level bearer tokens, accessing organization endpoints, and organization API endpoints. To request access to the APIs, contact team@cloudahoy.com.
Organization-Level Bearer Tokens
CloudAhoy can provide an organization-level bearer token for an API client that allows the client to interact with any user account that is a member of the organization as if the user has authorized the client individually.
This simplifies application integration with organizations by eliminating the need to have each user in the organization individually authorize the client application.
A single organization-level bearer token may specify multiple scopes.
Requesting or Revoking an Organization-Level Token
Contact team@cloudahoy.com to request or revoke an organization-level token. Include the organization and API client to which the token should apply or be revoked.
Accessing Organization Endpoints
When accessing an Organization API endpoint, e.g., integration/v1/org/flights, provide the organization-level token in the Authorization header:
Authorization: Bearer <org access token>
When necessary, the account within the organization to which the request applies will be specified as part of the request.
Organization API Endpoints
Documentation for the Organization-level APIs may be found in the following help topics:
Last Updated: