Better Email API
Use the Better Email API when an external system needs to manage data in Better Email. The first public API resource is recipient fields, which lets your systems create and maintain personalization fields for templates, merge tags, insertion, and segmentation.
The API is built for server-to-server integrations. Do not call it directly from browser code or expose API keys in client-side applications.
Base URL
https://app.better.email
All current public API endpoints use the /api/v1 prefix and return JSON.
Start here
- Quickstart shows the shortest path to making a first request.
- Authentication explains API keys and bearer tokens.
- Errors and conventions covers error responses, JSON behavior, browser requests, and versioning.
- Recipient fields reference documents the first public API resource.
Current API resources
| Resource | What it is for |
|---|---|
| Recipient fields | Create, list, update, and delete API-managed recipient fields. |
How API-managed recipient fields fit in
Recipient fields can come from a few places:
- manual fields created in the Better Email UI
- synced fields from supported ESP integrations
- API-managed fields created through the Better Email API
API-managed fields are marked with source: api. They can be listed and read alongside other recipient fields, but only fields created through the API can be changed or deleted through the API.