Open Morse

Reference

Broadcasts

2 routes, generated from Morse’s own OpenAPI document. Every path below hangs off the base URL, and every one needs the bearer header.

The examples are built from each route’s schema, so the shapes and types are exactly what the API declares. The values are illustrative, and no one has run them.

Who this link belongs to. **Read-only, deliberately.**

GET/unsubscribe/{token}

Mail clients and security gateways fetch the links in a message before anybody clicks them. A GET that opted somebody out would unsubscribe people who never asked, and the first they would know of it is the announcement they stopped getting. The opt-out is the POST below, which the page makes when they press the button. An unknown token answers 200 with no address rather than 404: the page says the same thing either way, and a 404 would tell somebody probing tokens which ones are real.

GET/unsubscribe/{token}

curl "$MORSE/unsubscribe/mp_YOUR_MORSE_TOKEN" \
  -H "Authorization: Bearer $MORSE_TOKEN"
200
{
  "done": true,
  "email": "priya@neuralarc.ai"
}

Stop sending this person broadcasts. No session: they are in their email.

POST/unsubscribe/{token}

Their meeting invitations, notes and booking emails are untouched — those are transactional, and the suppression this writes is read only by the broadcast sender (plan 040 R2, R3).

POST/unsubscribe/{token}

curl -X POST "$MORSE/unsubscribe/mp_YOUR_MORSE_TOKEN" \
  -H "Authorization: Bearer $MORSE_TOKEN"
200
{
  "done": true,
  "email": "priya@neuralarc.ai"
}