Bio link
The API
On the web
Every account has an API. Make a key under Settings → Account → Integrations, send it as a bearer token, and a script, a Zapier zap or your own CRM can read what is scheduled, read who came in through a page, and put a post on the calendar.
- 1Make a keySettings → Account → Integrations, under API keys. A key works in the workspace you have open when you make it. Name it after the tool it is for, choose Read only or Read and write, press Make a key.
- 2Copy itIt is shown once. MORR keeps a hash, not the key, so a lost key means a new one.
- 3Send it
Authorization: Bearer morr_…on every request, to the address printed in the section.
| Route | Does | Needs |
|---|---|---|
GET /v1/me | Who this key is and what it may do | read |
GET /v1/posts | The calendar. ?status=pending&from=&to=&limit= | read |
POST /v1/posts | Put a post on the calendar | write |
GET /v1/posts/:id | One post | read |
DELETE /v1/posts/:id | Take a post off | write |
GET /v1/leads | The CRM. ?status=new | read |
GET /v1/media | The library, newest first | read |
GET /v1/pages | Your bio pages with their public addresses | read |
From Claude or ChatGPT
The same key works as a connector. Under Settings → Account → Integrations is a second address ending in /mcp; add it to Claude as a custom connector (Settings, Connectors, Add custom connector) or to ChatGPT in developer mode, with the key as the bearer token, and the assistant gets eight tools: who the key is, the calendar, one post, put a post on, take one off, the leads, the library and the pages. Ask it to plan next week and it can read what is already there, write the posts, and put them on as drafts for you to read before they go, or straight on to go out at their times. Nothing it does publishes on its own: a post it adds goes out through the same publisher on the same schedule as one made by hand.
Putting a post on the calendar
Send JSON with caption, platform, scheduled_at as an ISO 8601 date-time, and optionally media_url, thumbnail_url, is_video, post_type and status (pending, or draft to hold it). The answer is the post as MORR stored it, with its id. It appears on the calendar and the phone the same as one made by hand, and publishes on the same schedule.
| Answer | Means |
|---|---|
| 401 | No key, or a revoked one |
| 403 | A read key trying to write |
| 400 | The body is missing something; the message says what |
| 404 | No such post, or no such route; the answer lists the routes |
| 429 | One key over its budget for the minute; ease off |