---
title: "Get pending invitation by ID"
method: GET
path: "/teams/{key}/invites/{inviteId}"
tags: ["Team Invites"]
---

# Get pending invitation by ID

`GET /teams/{key}/invites/{inviteId}`

Retrieve a pending team invitation by its ID. Team key can be ID or slug.

## Path parameters

- `key` string, required — Team identifier (ID or slug)
- `inviteId` string, required — Team invite ID to retrieve

## Response `200`

OK

- object
  - `invite` object, required — Pending team invitation. Automatically deleted after 7 days via DynamoDB TTL. When accepted, creates a TeamMember record and deletes the invitation.
    - `id` string, required — Unique identifier for the team invitation
    - `createdAt` string, date-time, required — Timestamp in ISO 8601 format when the invitation was created
    - `updatedAt` string, date-time, required — Timestamp in ISO 8601 format when the invitation was last updated
    - `teamId` string, required — Team this invitation is for
    - `email` string, email, required — Email address of the invited user. Used for sending invitation.
    - `permissions` string[], required — Permissions the user will receive upon accepting the invitation. Can be overridden per promoter or venue.
    - `roleIds` string[] — Role IDs assigned on invite acceptance. Effective permissions are role + explicit nodes.
    - `access` object — Promoter access to apply when the invitation is accepted.
      - `promoterIds` string[], nullable, required — Null means team-wide promoter access. An array means access is restricted to those promoters.
    - `token` string, required — Secure token for invite acceptance. Required to accept the invitation.
    - `expiresAt` integer, required — Unix timestamp (seconds) for DynamoDB TTL. Invitation will be automatically deleted after 7 days.
    - `invitedBy` string, required — User ID who sent the invitation
    - `tenantId` string, required — Tenant ID for multi-tenant isolation

## Other responses

- `400` — 400
- `401` — 401
- `403` — 403
- `404` — 404
- `409` — 409
- `412` — 412
- `422` — 422
- `429` — 429
- `500` — 500
- `501` — 501
- `503` — 503

---

[API](https://skmtc.net/session/apis/session-services-api.md) · [All operations](https://skmtc.net/session/apis/session-services-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/session/session-services-api/versions/a1bb6f6c8a2e/schema)