What changed in Sendly
Notable changes to the Sendly platform, newest first. Each entry is dated by when it landed in the product, and links to the documentation for it.
Last updated 2026-09-02
What is on this page
Changes to Sendly that you can see or use, newest first. Internal work — refactors, test infrastructure, deployment plumbing — is left off however large it was, because a changelog that lists everything is a changelog nobody reads.
Dates are when the change landed in the product, taken from this repository's history rather than chosen to make a release cadence look tidy.
2026-09-02 — JavaScript and Python SDKs reach 1.0.0
sendly-js is on npm and sendly-python is on PyPI, both at 1.0.0, both open source, and both generated from the published OpenAPI contract. send() targets the v1 API; the previous shape stays available as sendLegacy for anyone mid-upgrade.
2026-08-31 — Partial grants: an agent gets the permissions you tick, and no others
The MCP consent screen became a checkbox list rather than a single yes. The permissions that produce effects nothing in the dashboard undoes — sending mail, sending a campaign, enabling a workflow, removing a suppression, and the rest — now arrive unchecked, each with a sentence naming the consequence. Tools outside the grant are never registered, so an agent cannot see them.
2026-08-20 — Guided DNS setup publishes your records and then watches them
Domain verification stopped being a copy-and-paste exercise against your registrar. Sendly can publish the SPF, DKIM and DMARC records for you and keep checking them afterwards, so a record someone edits or a registrar migration drops is noticed rather than discovered through a delivery failure.
2026-08-18 — A remote MCP server, so an AI agent can work in your account
Sendly began answering the Model Context Protocol at app.sendly.now/api/mcp over Streamable HTTP, authorized by OAuth 2.1 with PKCE or by a secret key. The tool registry is filtered per request against the credential's own scopes, so what an agent can see is decided before it asks.
2026-07-19 — Five provider dialects: keep your SDK, change two variables
Compat endpoints landed for Resend, SendGrid, Postmark, Mailgun and Plunk. Each parses that vendor's transactional-send request shape and runs it through Sendly's own pipeline, so an existing integration moves by changing a base URL and a key rather than by being rewritten.
2026-06-11 — Mailboxes: receive real mail on your own domain
Sendly stopped being send-only. Mailboxes on your domain are reachable over IMAP and SMTP with app passwords you manage, and the messages are also projected into the API so your own code can read them.
Following along
The API contract itself is published, so the most precise way to see what changed is to diff it: the released OpenAPI document is served at docs.sendly.now/openapi.json, and both official SDKs check themselves against it. Breaking changes to the v1 surface are not made quietly.
The SDKs are open source on GitHub, where their own release notes carry the client-library detail this page does not.
Questions people ask
- How often is this page updated?
- When something a user can see or use ships. There is no fixed cadence and no filler: a month with no entry is a month whose changes were internal.
- Where do the dates come from?
- The date the change landed in the product, taken from this repository's history. An entry with no defensible date does not go on the page.
- How do I find out about API changes specifically?
- Diff the published OpenAPI document at docs.sendly.now/openapi.json. It is the released contract rather than a description of it, both official SDKs check themselves against it, and it is the most precise answer to what changed.
Something on this page out of date, or missing the case you are in? Write to support@sendly.now — we answer our own email. The full technical detail lives in the documentation.