Changelog — relaybell docs

Changes that matter when you build on relaybell, newest first. Changes inside the dashboard are in the setup guide.

2026-10-21: docs in the new site, and relaybell for AI assistants

Developer docs

The docs are now one page per topic at /docs, with search (Ctrl/⌘ K), an "On this page" outline and a Copy page menu (copy as Markdown, or open the page in ChatGPT or Claude).
New install guides for Next.js, React and Vue and Nuxt.
Every page has a Markdown copy at /docs/<page>.md, and /llms.txt lists them all. Old links such as /docs#webhooks still land on the right page.

AI assistants (MCP)

relaybell-mcp lets Claude Desktop, Claude Code, Cursor and VS Code read your results, segments and topics, draft a notification, send a test to your own devices and, after you confirm a summary, send it. It can't delete anything, create keys or change settings. Set it up from Settings → Developers → Use relaybell from your AI assistant, or see AI assistants.

Webhooks

A new signature header, X-Relaybell-Webhook-Signature: t=<unix seconds>,v1=<hex HMAC-SHA256>, signs the timestamp and the raw body together, so an old request can't be replayed. The older X-Relaybell-Signature header is still sent unchanged, so existing receivers keep working. See Verify a webhook signature.
New headers X-Relaybell-Event (the event name) and X-Relaybell-Delivery (the delivery id, the same on every retry and resend: de-duplicate by it).
Failed deliveries are retried 5 times over about 10 hours. A 410 Gone answer means the receiving end no longer exists (for example a deleted Zap): retries stop and the webhook is turned off, and the account owner is emailed.
A 30-day delivery log, resend and test events: GET /api/v1/webhooks/:id/deliveries and POST /api/v1/webhooks/:id/test. See Delivery log, resend and test events.
A webhook that keeps failing (3 days, or 50 deliveries in a row) is turned off. See When a webhook keeps failing.

Server SDKs 1.2.0 (Node.js on npm as relaybell, PHP on Packagist as relaybell/relaybell-php; the Python 1.2.0 build is in the zip download)

Webhook verification in one call: Node verifyWebhook(), Python verify_webhook(), PHP Relaybell\Webhook::verify().
Reading your sends: listNotifications() and getNotification() (Python list_notifications() and get_notification()).
Node: TypeScript types, and an error when the client is created in a browser, where your API key would be exposed.
Python: snake_case keyword arguments (external_id, segment_id, send_at, …) are turned into the API's camelCase fields.
Details: Server SDKs.

API reference

The REST API as an OpenAPI 3.1 document at /openapi.json: every customer endpoint, with the API key scope each one needs (x-scope).
API reference: every endpoint with its scope, parameters, request body, responses, error codes and code samples, generated from that document.
/llms-full.txt now ends with a list of every endpoint and the scope it needs.

The version submitted to the wordpress.org plugin directory. Mostly changes asked for by its review rules:

The settings page's styles and scripts are regular files loaded through WordPress's script and style queues; the page works as before.
The "Notify me when back in stock" button's markup is escaped when it is printed.
The relaybell host under Advanced must be an https:// address.
The clean-up when you delete the plugin uses prepared database queries; it removes the same data as before.
The status panel says "1 subscriber" instead of "1 subscribers".

Version 1.2.4 added identity verification for logged-in visitors. See WordPress & WooCommerce.

/llms-full.txt: everything an AI assistant needs in one text file (key facts, the developer docs, the setup guide and the plans). /llms.txt, the shorter index, is built from the same facts.
The developer docs as Markdown: /docs.md, and one file per section.
The developer docs were checked against the code and corrected.