Skip to main content
GET
Get your current organization

Authorizations

Authorization
string
header
required

Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.

Console sessions (Clerk JWTs) act for the signed-in user. To act for a team instead, also send X-Team-Id: <team_id>; it applies only when the user owns or belongs to that team, otherwise the request runs against the user's own account. API keys created inside a team already act for that team and do not need the header.

Response

OK

The authenticated caller's current organization.

id
string
required

Organization ID.

Example:

"org_id_abc_123"

name
string
required

Organization name.

Example:

"my-org"

Last modified on October 13, 2026