Skip to main content
GET
Get your account

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 account the API key belongs to.

id
string
required

Account ID. For a request that acts for a team (a key created inside the team, or X-Team-Id) this is the team owner's account. For an organization member it is the member's own account; see GET /v2/organization for the organization.

Example:

"user_2abc123"

email
string | null
required

Email of the same account. Null when the account has no email on file.

Example:

"dev@example.com"

Last modified on November 13, 2026