Skip to content

Errors

Blocked Recipient Email

A recipient email address is blocked because it hard bounced or was reported as spam. Check the address, or contact support to unblock it.

What Happened

A recipient’s email address is on the SignatureAPI blocklist, so the API refuses to use it. An address gets blocked after a hard bounce (for example, the mailbox does not exist) or after the account owner marked our email as spam.

The API returns this error with a 422 status when you add a recipient with a blocked address. It returns it with a 409 status when you resend a request or create a ceremony for a recipient whose address is blocked.

Example response

422 Unprocessable Content (application/problem+json)
{
  "type": "https://signatureapi.com/docs/v1/errors/blocked-email",
  "title": "Blocked Recipient Email",
  "status": 422,
  "detail": "Email address jane.doe@example.com is blocked."
}

How to Fix

  • Check the address for typos. This is the most common cause.
  • If the address is correct, ask the recipient to confirm that the mailbox is active and can receive mail.
  • If the recipient marked our email as spam, ask them to allow messages from SignatureAPI.
  • To keep using the same address, contact support to have it unblocked. Otherwise, replace the recipient with a different address.

  Still stuck? Contact support.