---
title: "Create Project Invite"
method: POST
path: "/api/v1/projects/{project_id}/invites"
tags: ["project-invites"]
---

# Create Project Invite

`POST /api/v1/projects/{project_id}/invites`

## Path parameters

- `project_id` string, uuid, required

## Request body

- CreateProjectInviteRequest — No `role` and no `access_level`. A project grant is admission; an external guest holds no org role, so there is nothing to choose (spec §3.2's ruling).
  - `email` string, required

## Response `201`

Successful Response

- ProjectInviteCreated — The invite plus its one-time link. The link IS the delivery mechanism — PR3 ships no SMTP for project invites (spec §10's flow is link-first and hermetic; council ruling D2). Resend returns a fresh one because it rotates the token, so the previous link is dead and rendering it would hand the admin a URL that no longer works.
  - `invite` ProjectInvite, required
    - `id` string, uuid, required
    - `project_id` string, uuid, required
    - `email` string, required
    - `status` 'pending' | 'accepted' | 'revoked' | 'expired', required
    - `invited_by` string, uuid, nullable, required
    - `expires_at` string, date-time, required
    - `accepted_by` string, uuid, nullable, required
    - `accepted_at` string, date-time, nullable, required
    - `created_at` string, date-time, required
  - `link` string, required

## Other responses

- `4XX` — Client Error
- `5XX` — Server Error

---

[API](https://skmtc.dev/rudus/apis/rudus-api.md) · [All operations](https://skmtc.dev/rudus/apis/rudus-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/rudus/rudus-api/revisions/f149124a4d80/schema)