Skip to main content
GET

Overview

Returns the organization context for the caller: the profile ID, the organization, and the caller’s role in it. The Danube MCP server uses it to attribute requests to an organization. Clients can use it to learn which organization a key is bound to before generating a team .mcp.json (see Get MCP JSON). Auth: Accepts either JWT or API key (danube-api-key header). Resolution order:
  1. An explicit organization selector, the org_id query parameter or the danube-org-id header (the query parameter wins when both are sent). The caller must be a member. A non-member gets 404, not 403, so organization IDs are not leaked.
  2. Otherwise, for an API key caller, the organization the key is bound to. Keys without a bound organization fall back to the owner’s personal organization.
  3. Otherwise, for a JWT caller, the personal organization.
The Python and TypeScript SDKs do not wrap this endpoint yet. Call it directly.

Query Parameters

string
Organization UUID to resolve. Requires membership.

Headers

string
Same as org_id. Ignored when the query parameter is present.

Response

string
The caller’s profile ID
string
The resolved organization UUID
string
Organization display name. null if the organization row could not be loaded.
string
Organization URL slug. null if the organization row could not be loaded.
string
The caller’s role in the organization: owner, admin, member or viewer. null if the key’s owner is not a member of the key’s bound organization.

Errors

Example