---
title: "Accept a presentation invite (attach the grant to the caller)."
method: POST
path: "/presentations/{slug}/accept"
tags: ["Presentations"]
---

# Accept a presentation invite (attach the grant to the caller).

`POST /presentations/{slug}/accept`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/presentations/{slug}/accept`
- Auth: HTTP bearer

The endpoint the invite email's CTA lands at after the recipient signs in / signs up. The single-use token comes from the body `{token}` or the `?token=` query param; it's hashed and matched to a pending grant for THIS presentation. On success the grant is attached to the caller (user_id + accepted_at set, token consumed) and the caller's tier is returned. The invite email is address-specific: the caller's account email MUST match the grant email (case-insensitive) or a 403 is returned. Authed user. Requires an `Idempotency-Key` header. MNE-1428.

## Path parameters

- `slug` string, required

## Query parameters

- `token` string

## Headers

- `Idempotency-Key` string, required

## Request body

- object
  - `token` string: The single-use invite token.

## Response `200`

Invite accepted (or idempotently already accepted by this caller). Returns the presentation + the caller's tier.

- object
  - `presentation` object, required
    - `id` string, uuid, required
    - `slug` string, required: URL-safe id, e.g. 'inside-mnemom'.
    - `title` string, required
    - `agent_id` string, nullable: The presentation's agent (e.g. Aletheia). prod agents.id; no FK.
    - `status` 'draft' | 'live' | 'archived', required
    - `created_by` string, uuid, required: auth.users.id of the minting admin.
    - `created_at` string, date-time, required
    - `updated_at` string, date-time, required
  - `tier` 'L1' | 'L2' | 'L3', required
  - `accepted` boolean
  - `already_accepted` boolean

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `410`: The invite has expired.
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

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