---
title: "List Pending Invitations"
method: GET
path: "/v1/orgs/{org_id}/invitations"
tags: ["Org Members"]
---

# List Pending Invitations

`GET /v1/orgs/{org_id}/invitations`

## Request

- Base URL: `https://api.robosystems.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.robosystems.ai/v1/orgs/{org_id}/invitations`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Requires admin or owner role.

## Path parameters

- `org_id` string, required

## Response `200`

Successful Response

- OrgInvitationListResponse: List of pending organization invitations response.
  - `invitations` OrgInvitationResponse[], required
    - `id` string, required
    - `org_id` string, required
    - `email` string, required
    - `role` 'owner' | 'admin' | 'member', required
    - `status` string, required
    - `invited_by_user_id` string, required
    - `invited_by_name` string, nullable, required
    - `created_at` string, date-time, required
    - `expires_at` string, date-time, required
    - `is_expired` boolean, required
    - `token` string, nullable: Test-support only: the raw invite token. Populated ONLY when AUTH_INVITE_TOKEN_IN_RESPONSE is enabled in a non-production environment; always null in production. Lets automated authorization tests complete the invite -> register flow without email interception.
  - `total` integer, required
  - `org_id` string, required

## Other responses

- `400`: Invalid request
- `401`: Authentication required
- `403`: Access denied
- `404`: Resource not found
- `422`: Validation Error
- `429`: Rate limit exceeded
- `500`: Internal server error

---

[API](https://skmtc.dev/robosystems/apis/robosystems-api.md) · [All operations](https://skmtc.dev/robosystems/apis/robosystems-api/llms.txt) · [OpenAPI document](https://skmtc.dev/robosystems/apis/robosystems-api/revisions/e661e2d5ca6a?raw)