Skip to main content
POST
/
api
/
people
Create a person
curl --request POST \
  --url https://archyon.app/api/people \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": "<string>",
  "name": "<string>",
  "email": "<string>",
  "photoUrl": "<string>",
  "title": "<string>",
  "bio": "<string>",
  "contact": {},
  "clerkUserId": "<string>",
  "properties": {}
}
'
{
  "person": {
    "id": "<string>",
    "orgId": "<string>",
    "name": "<string>",
    "bio": "<string>",
    "contact": {},
    "properties": {},
    "createdAt": 123,
    "updatedAt": 123,
    "email": "<string>",
    "photoUrl": "<string>",
    "title": "<string>",
    "clerkUserId": "<string>"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.archyon.app/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Both Clerk session JWTs (browser) and Archyon Personal Access Tokens (an_pat_…, server / CLI / MCP) use the same Bearer header. The server distinguishes them by token shape.

  • Clerk JWTs carry org context in the token claims (org_id, org_role, org_slug) — required for org-scoped endpoints. Configure your Clerk session template to include these claims; see DEPLOYMENT.md.
  • PATs are minted at /account → Tokens. Each PAT is bound to whichever org was active at mint time. Switch orgs and re-mint to address a different org.

Body

application/json
​
id
string
required
​
name
string
required
​
email
string
​
photoUrl
string
​
title
string
​
bio
string
​
contact
object
​
clerkUserId
string
​
properties
object

Response

Created.

​
person
object
required