Bounces and complaints

Report a hard bounce

POST /api/v1/notification/bounce

For a message sent through a server that does not report bounces by itself. The address is blacklisted and the bounce is recorded on the message. Soft bounces need no report. An admin token may report any message; a customer's token, only its own.

Request body application/x-www-form-urlencoded
message_id string required
The Message-ID the email was sent with.
description string
The bounce message.
Responses
200 The bounce, as recorded (also when it was recorded already).
400 message_id is missing, or no message of the token's account was sent with it.
401 The token is missing or wrong (Unauthenticated.), or its user may not act on this object (Unauthorized). Without the Accept: application/json header, a missing or wrong token answers with a redirect to the sign-in page instead.
Report a hard bounce
1 2 3 4 5
curl -X POST 'https://your-domain/api/v1/notification/bounce' \
  -H "Accept: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  --data-urlencode 'message_id=201637442604422402.6199642caf7f3@example.com' \
  --data-urlencode 'description=550 5.1.1 User unknown'
Response
{
    "id": 5021,
    "runtime_message_id": "201637442604422402.6199642caf7f3@example.com",
    "message_id": null,
    "customer_id": 1,
    "tracking_log_id": 88231,
    "bounce_type": "hard",
    "status_code": null,
    "raw": "550 5.1.1 User unknown",
    "created_at": "2026-11-14T10:00:00.000000Z",
    "updated_at": "2026-11-14T10:00:00.000000Z"
}