Developers
There is no second, lesser API for customers
The product is built on the same API you get. Send events, write posts, manage brands and channels, render a clip and download it.
Send something that happened
One call, and every subscribed channel posts it
Every channel subscribed to that stream renders the event and publishes it, in its own language, wearing its own brand.
curl https://api.reelwire.io/v1/stream \
-H "Authorization: Bearer rw_your_key_here" \
-H "Content-Type: application/json" \
-d '{
"streamId": "st_c3efd7ec00dd",
"eventId": "01M2RSYXAQA155XE1ZYGPG51FA",
"occurredAt": "2026-09-18T09:00:00Z",
"data": { "headline": "EUR/USD breaks 1.10", "subline": "First time since March" }
}' eventId is the idempotency key: sending the same one
twice does not post twice, which is what makes a retry safe. What belongs in
data is published as a JSON schema per template, so a
client can be generated rather than guessed.
Keys carry permissions
A key holds only what you gave it
Per area of the product: sending data, posts, post lists, approvals, media, brands, channels, feeds and streams, templates, renders, webhooks, each read or write. No key at all can change the plan, buy allowance, touch invoices, invite somebody, create another key or reach another workspace: money and people are for a person who signed in. A refused request names the permission that is missing and where to add it, rather than answering 403 and leaving you to guess.
- Send raw data. For a producer or a trading system that only pushes events in.
- Make and publish posts. Posts, post lists, media and renders. Reads brands and channels.
- Read only. Reporting and dashboards. Sees everything, changes nothing.
For AI assistants
An MCP server, which is the same API again
The same API as tools an assistant can call, with the documentation bundled beside them so it can look something up before it acts. It authenticates with an ordinary API key, so the key's permissions are the whole of what the assistant can do: give it a read-only key and it can answer questions about what went out and cannot publish anything.
{
"mcpServers": {
"reelwire": { "type": "http", "url": "https://mcp.reelwire.io/mcp" }
}
} The whole of it
Read the reference before you write a line
Every endpoint, every permission and every template schema, with the awkward parts written down rather than left to be discovered.
