REST API · v1

API Reference

Manage campaigns, lists, contacts, servers and more over a consistent JSON REST API. Every request is authenticated with a Bearer token.

Authentication

Send your API token as a Bearer token on every request. Tokens are created per customer under your account’s API settings.

HTTP 
Authorization: Bearer YOUR_API_TOKEN
Accept: application/json
cURL 
curl https://getmailpurse.com/api/v1/lists \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/json"

Base URL: https://getmailpurse.com/api · OpenAPI spec

Guides

Errors and status codes

Code Meaning 200 Success 401 Missing or invalid API token 403 Authenticated, but the account lacks the required permission 404 Resource not found (or not owned by the token’s…

Getting started with the API

The MailPurse REST API exposes your account’s lists, contacts, campaigns, servers and billing over JSON over HTTPS. All endpoints are prefixed with /api.

Authentication

Every API request is authenticated with a personal Bearer token (Laravel Sanctum).

Pagination and rate limits

List endpoints return paginated results. Use the page query parameter and inspect the response meta: { "data": [ … ], "meta": { "current_page": 1, "last_page": 4, "per_page": 15,…

Endpoints · 83

Email Lists

Contacts

Campaigns

Automations

Transactional Emails

Delivery Servers

Bounce Servers

Reply Servers

Sending Domains

Tracking Domains

Integrations

Billing