Skip to main content

EmailMassivo public API

The EmailMassivo public API lets you send transactional emails, work with your contact base, read campaigns, and receive delivery events.

The public API follows REST principles: predictable, resource-oriented URLs, JSON in request and response bodies, and standard HTTP status codes.

How requests work​

Base URL: https://api.emailmassivo.com/api

Authentication. Every request requires a Bearer token in the Authorization header. A token works only where it has scopes: for example, sending emails needs email.send, and the example below needs contacts.read. See Authentication for details.

curl https://api.emailmassivo.com/api/v1/public/lists \
  -H "Authorization: Bearer $API_TOKEN"

Request body format. Every endpoint accepts and returns application/json. Standard public API responses are wrapped in an envelope with ok, data, and meta fields:

{
  "ok": true,
  "data": { },
  "meta": { "requestId": "550e8400-e29b-41d4-a716-446655440000", "timestamp": "2026-09-30T10:15:00.120Z" }
}

data is the endpoint's payload: a resource object, or an array for list endpoints. meta.requestId is the request identifier you can quote to support for tracing.

Errors. On any error, the public API returns a 4xx/5xx status code and a body with "ok": false, an error object (fields code and message), and meta. When contacting support, pass meta.requestId from this response. Error tables live on the individual endpoint pages — for example, Send error codes.

Idempotency. The send endpoint accepts an Idempotency-Key header to guard against duplicates on network retries — see Idempotency and quota.

Specification. A machine-readable description of the API in OpenAPI 3.0 format is available at /docs/openapi.json — use it to generate clients or to import into Postman, Insomnia, and similar tools.

Where to start​

First time here? Authentication → Quickstart.

Already know what you need?