Skip to main content
GET
Get a pending organization invite

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.

Path Parameters

id
string
required

Invite identifier

Response

OK

A pending invitation to join the caller's organization. An invite stops being listed once it is accepted, revoked or expired.

id
string
required

Invite ID.

Example:

"invite_id_abc_123"

email
string
required

Email address the invitation was sent to. The invitee accepts by signing in with a verified account on this address.

Example:

"new-member@example.com"

role
object
required

An organization role, by ID and display name.

createdAt
string<date-time>
required

When the invite was sent.

Example:

"2026-10-01T09:00:00Z"

expiresAt
string<date-time>
required

When the invite can no longer be accepted.

Example:

"2026-10-15T09:00:00Z"

Last modified on November 3, 2026