Meeting Types

Create a meeting type

Create ONE meeting type from `{ name, emoji? }`. Names are unique per user — a duplicate returns 400. **Requires `Idempotency-Key`.** Returns `{ data: { meeting_type: {...} } }` with status 201.

POST /v2/meeting-types/

Parameters

Header parameters

Idempotency-Key
string required
Required. UUID per logical operation, reused on every retry. See apps/rest-api/src/shared/idempotency.ts for the full contract. Missing → 400 BadRequest; same key + different body → 409 Conflict.

Request body

Content-Type: application/json

name
string required
emoji
string

Example

{
  "name": "string"
}

Responses

201 — Created

Content-Type: application/json

data
object required
data.meeting_type
object required
data.meeting_type.id
string (uuid) required
data.meeting_type.user_id
string
data.meeting_type.name
string required
data.meeting_type.emoji
string | null
data.meeting_type.created_at
string (date-time) required

Example

{
  "data": {
    "meeting_type": {
      "id": "00000000-0000-0000-0000-000000000000",
      "name": "string",
      "created_at": "2026-09-17T02:39:21.279Z"
    }
  }
}

400 — Request body failed validation.

Content-Type: application/json

(body)
any

401 — Missing or invalid API key.

Content-Type: application/json

(body)
any

403 — Valid key, insufficient permission.

Content-Type: application/json

(body)
any

404 — Resource does not exist.

Content-Type: application/json

(body)
any

409 — Request conflicts with the current state of the resource.

Content-Type: application/json

(body)
any

429 — Rate limit exceeded.

Content-Type: application/json

(body)
any

500 — Unexpected server error.

Content-Type: application/json

(body)
any

Code samples

curl https://api.prod.getdex.com/v2/meeting-types/ \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "string"
}'
Copyright © 2026