Endpoints
Organizations APIs require
workspaceId in context (supplied automatically by workspace-scoped API keys). Read endpoints use the organizations:read scope; mutations require organizations:write.Key concepts
- Organization create/update payloads accept both camelCase and snake_case keys (
legalName/legal_name, etc.). The API normalizes them before storing in the database. - Capabilities allow segmenting organizations by category (
transport,accommodation,flight,experience,other) and optional mode identifiers/keys. - Deletions return
{ ok: true }when successful; attempting to delete a missing organization returns404. - API Keys: Organizations can have their own API keys for B2B integrations. These keys are scoped to specific products and capabilities.