[relaybell docs › Reference › Changelog](https://relaybell.com/docs/changelog) · [All docs as Markdown](https://relaybell.com/docs.md) · [Index for AI assistants](https://relaybell.com/llms.txt)

# Changelog

> What changed for developers: the docs in the new site and relaybell for AI assistants; webhooks v2, server SDKs 1.2.0 and the OpenAPI reference; WordPress plugin 1.2.5.

Changes that matter when you build on relaybell, newest first. Changes inside the dashboard are in the [setup guide](https://relaybell.com/guide).

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

**Developer docs**

- The docs are now one page per topic at [/docs](https://relaybell.com/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](https://relaybell.com/docs/install-nextjs), [React](https://relaybell.com/docs/install-react) and [Vue and Nuxt](https://relaybell.com/docs/install-vue).
- Every page has a Markdown copy at `/docs/<page>.md`, and [/llms.txt](https://relaybell.com/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](https://relaybell.com/docs/ai-assistants).

## 2026-10-20: webhooks v2, server SDKs 1.2.0 and the API reference {#2026-10-20}

**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](https://relaybell.com/docs/webhooks#webhook-verify).
- 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](https://relaybell.com/docs/webhooks#webhook-deliveries).
- A webhook that keeps failing (3 days, or 50 deliveries in a row) is turned off. See [When a webhook keeps failing](https://relaybell.com/docs/webhooks#webhook-auto-disable).

**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](https://relaybell.com/relaybell-python-sdk.zip))

- 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](https://relaybell.com/docs/server-sdks).

**API reference**

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

## 2026-10-19: WordPress plugin 1.2.5 {#2026-10-19-wordpress}

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](https://relaybell.com/docs/identity) for logged-in visitors. See [WordPress & WooCommerce](https://relaybell.com/docs/install-wordpress).

## 2026-10-19: docs for AI assistants {#2026-10-19-docs}

- [/llms-full.txt](https://relaybell.com/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](https://relaybell.com/llms.txt), the shorter index, is built from the same facts.
- The developer docs as Markdown: [/docs.md](https://relaybell.com/docs.md), and one file per section.
- The developer docs were checked against the code and corrected.