API ReferenceAPI Error Codes

    API Error Codes

    Interpret errors returned by Simply Send’s public email sending and Web Setup APIs, and choose a safe next step.

    Use credentials created in the region selected above. Changing the documentation region updates examples; it does not move your account or resources.

    Read the response

    The response includes a numeric HTTP status (for example, 400) as well as a string error code in reasonCode or error.code. The tables below list the HTTP status number returned with each code. Some codes can be used by more than one endpoint, so their status can vary by endpoint. Read the response message too; it can identify the field, resource, or limit that needs attention.

    Dashboard links in the remedy column open the portal for the region selected in the documentation menu.

    HTTP status codes

    Error codeWhat it meansWhat to do
    400 Bad RequestThe body, field value, parameter, or combination of fields is invalid.Read the response message and correct the named field. Send JSON with the documented types and required values.
    401 UnauthorizedThe API key is missing or not accepted for this request.Use an active key of the correct type for the selected API and region. Check the X-Api-Key header on the API Keys page.
    403 ForbiddenThe key, role, workspace, subscription, sender identity, or sending state does not allow this operation.Check the key permissions and workspace access under Account → Workspaces. Contact your administrator or Simply Send support if access is unexpected.
    404 Not FoundThe route or resource does not exist in this workspace.Check the endpoint and resource ID. Confirm the resource belongs to the workspace authenticated by this key.
    409 ConflictThe request conflicts with the current resource state or another request is still in progress.Refresh the resource state before retrying. For sends, follow the Idempotency-Key retry guidance.
    413 Payload Too LargeThe request exceeds the endpoint or gateway size limit.Reduce the payload or use the transactional attachments API.
    429 Too Many RequestsA request rate, send rate, or resource quota has been exceeded.Back off for rate limits. For resource quotas, review Account → Limits or the rate limits guide.
    5xx Server ErrorA service or dependency failed while processing the request.Retry safe reads with backoff. Before retrying a send, inspect Email Events and reuse its Idempotency-Key. If the issue continues, contact support with the timestamp, request ID, HTTP status, and response body.

    Transactional and marketing send codes

    The send dispatcher may return these values in reasonCode. Each code has its own row; read the response message for request-specific details.

    Error codeHTTP statusWhat it meansWhat to do
    BAD_REQUEST400 Bad RequestThe send request could not be parsed as a valid request.Send a JSON object and include the required fields for this endpoint. POST /attachments accepts attachment data only; send email fields to POST /send.
    INVALID_REQUEST_BODY400 Bad RequestThe request body is missing, malformed, or is not a JSON object.Send a JSON object and include the required fields for this endpoint. POST /attachments accepts attachment data only; send email fields to POST /send.
    MISSING_REQUIRED_FIELDS400 Bad RequestOne or more required send fields are missing.Send a JSON object and include the required fields for this endpoint. POST /attachments accepts attachment data only; send email fields to POST /send.
    API_AUTHENTICATION_REQUIRED401 UnauthorizedThe request does not include the required API authentication.Use the matching key from API Keys and account ID from the same region. See Authentication.
    INVALID_X_ID400 Bad RequestThe X-Id header is missing or is not a valid account identifier.Use the matching key from API Keys and account ID from the same region. See Authentication.
    INVALID_ACCOUNT_ID400 Bad RequestThe supplied account ID is malformed or invalid.Use the matching key from API Keys and account ID from the same region. See Authentication.
    INVALID_FROM_FIELD400 Bad RequestThe from field does not have an accepted sender format.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_FROM_ADDRESS400 Bad RequestThe sender email address is not syntactically valid.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_TO_FIELD400 Bad RequestThe to field contains no valid recipient address.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_TO_FIELD_FORMAT400 Bad RequestThe to field uses a format that cannot be parsed.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_CC_FIELD400 Bad RequestThe cc field contains no valid recipient address.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_CC_FIELD_FORMAT400 Bad RequestThe cc field uses a format that cannot be parsed.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_BCC_FIELD400 Bad RequestThe bcc field contains no valid recipient address.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_BCC_FIELD_FORMAT400 Bad RequestThe bcc field uses a format that cannot be parsed.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_RECIPIENT_ADDRESS400 Bad RequestAt least one recipient address, including an SMTP envelope recipient, is invalid.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_REPLY_TO_ADDRESS400 Bad RequestThe replyTo address is not valid.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    NO_RECIPIENTS_PROVIDED400 Bad RequestNo recipient was supplied in to, cc, or bcc.Correct the address syntax, provide at least one recipient and use a verified sender domain. For marketing sends, use only the to field.
    INVALID_TAG400 Bad RequestThe optional tag is empty, too long, or contains characters outside ASCII letters and digits.Remove punctuation, spaces, and non-ASCII characters, or omit the tag.
    CC_NOT_SUPPORTED_FOR_MARKETING400 Bad RequestA marketing request includes the unsupported cc field.Use the documented fields for the selected API. See Marketing Send and Transactional Send.
    BCC_NOT_SUPPORTED_FOR_MARKETING400 Bad RequestA marketing request includes the unsupported bcc field.Use the documented fields for the selected API. See Marketing Send and Transactional Send.
    ATTACHMENTS_NOT_SUPPORTED_FOR_MARKETING400 Bad RequestA marketing request includes attachments, which marketing sends do not support.Use the documented fields for the selected API. See Marketing Send and Transactional Send.
    CAMPAIGN_ID_NOT_SUPPORTED400 Bad RequestA transactional request includes campaignId, which is only supported by marketing sends.Use the documented fields for the selected API. See Marketing Send and Transactional Send.
    CONTACT_LIST_ID_NOT_SUPPORTED400 Bad RequestA transactional request includes subscriptionGroupId, which is only supported by marketing sends.Use the documented fields for the selected API. See Marketing Send and Transactional Send.
    MIXED_BCC_RECIPIENTS_DISABLED400 Bad RequestThe workspace does not allow BCC recipients alongside To or Cc recipients.Enable “Allow Bcc with To or Cc” under Account → Configurations, or use BCC-only / To-and-Cc-only recipients.
    WORKSPACE_CONFIGURATION_UNAVAILABLE503 Service UnavailableThe service could not load workspace settings required to validate the send.Retry later with the same idempotency key. Contact support if the error continues.
    TOO_MANY_ATTACHMENTS400 Bad RequestThe request exceeds the maximum number of attachments.Follow the attachment format and limits. For larger transactional messages use POST /attachments and include its submission ID in POST /send. Retry a server-side preparation failure with the same key.
    TOO_MANY_ATTACHMENT_RECIPIENTS400 Bad RequestAn attachment submission has more than the supported number of recipients.Follow the attachment format and limits. For larger transactional messages use POST /attachments and include its submission ID in POST /send. Retry a server-side preparation failure with the same key.
    INVALID_ATTACHMENT_REQUEST400 Bad RequestThe attachment endpoint received fields or a body shape it does not accept.Follow the attachment format and limits. For larger transactional messages use POST /attachments and include its submission ID in POST /send. Retry a server-side preparation failure with the same key.
    ATTACHMENT_PREPARATION_ERROR500 Internal Server ErrorThe service could not prepare one or more attachments for sending.Follow the attachment format and limits. For larger transactional messages use POST /attachments and include its submission ID in POST /send. Retry a server-side preparation failure with the same key.
    EMAIL_BODY_SIZE_EXCEEDED400 Bad RequestThe email body and metadata exceed the allowed body-size limit.Reduce body and metadata size. Marketing email is limited to 2 MiB total. For larger transactional messages, request an increase under Account → Approvals and use attachment upload. Retry limit lookup failures later; contact support if they persist.
    EMAIL_SIZE_EXCEEDED400 Bad RequestThe complete email exceeds the size limit configured for this workspace or email type.Reduce body and metadata size. Marketing email is limited to 2 MiB total. For larger transactional messages, request an increase under Account → Approvals and use attachment upload. Retry limit lookup failures later; contact support if they persist.
    EMAIL_SIZE_LIMIT_UNAVAILABLE503 Service UnavailableThe service could not determine the size limit configured for this workspace.Reduce body and metadata size. Marketing email is limited to 2 MiB total. For larger transactional messages, request an increase under Account → Approvals and use attachment upload. Retry limit lookup failures later; contact support if they persist.
    MISSING_TEMPLATE_VARIABLES400 Bad RequestThe message template references one or more variables with no supplied value.Add every variable named in the response to templateVariables or the template. See Templates and Compliance Templates.
    GLOBAL_UNSUBSCRIBE400 Bad RequestThe recipient has globally unsubscribed and cannot receive this marketing message.Send only to recipients with valid consent. Do not retry to bypass an unsubscribe; see the double opt-in guide for permitted resubscription flows.
    PLACEHOLDER_RECIPIENT_DOMAIN_NOT_ALLOWED400 Bad RequestA live workspace is attempting to send to a blocked placeholder recipient domain.Use a real recipient address for live mail. For testing, follow the sandbox testing guide.
    SANDBOX_RECIPIENT_NOT_ALLOWED400 Bad RequestThe recipient is not one of the supported sandbox simulation addresses.Use a real recipient address for live mail. For testing, follow the sandbox testing guide.
    SANDBOX_RECIPIENT_NOT_ALLOWED_IN_LIVE_WORKSPACE400 Bad RequestA sandbox simulation address was submitted from a live workspace.Use a real recipient address for live mail. For testing, follow the sandbox testing guide.
    SANDBOX_SUBSCRIPTION_REQUIRED403 ForbiddenThe sandbox workspace’s parent does not have the required active paid subscription.Check subscription status under Account → Billing. Contact support if the active plan is not recognized.
    SUBSCRIPTION_NOT_ACTIVE403 ForbiddenThe workspace does not have an active subscription for sending.Check subscription status under Account → Billing. Contact support if the active plan is not recognized.
    NO_PLAN_FOUND403 ForbiddenThe service could not find an eligible plan for this workspace.Check subscription status under Account → Billing. Contact support if the active plan is not recognized.
    SENDING_PAUSED403 ForbiddenSending is paused for this workspace.Review the portal notice and account status. Resolve the listed issue or contact support to request a review.
    RECIPIENT_DOMAIN_SUPPRESSED400 Bad RequestThe recipient domain matches an active suppression rule.Do not retry to bypass suppression. Review the address in Email Events or suppression state in Suppressions; see the Deliverability API.
    ALL_RECIPIENTS_SUPPRESSED400 Bad RequestEvery recipient in the request is suppressed or otherwise ineligible for delivery.Do not retry to bypass suppression. Review the address in Email Events or suppression state in Suppressions; see the Deliverability API.
    CAMPAIGN_NOT_FOUND404 Not FoundThe campaignId does not identify a campaign available to this workspace.Check campaignId and the selected workspace. See Marketing API.
    EMAIL_RATE_LIMIT_EXCEEDED429 Too Many RequestsThe workspace has exceeded its current email sending rate.Wait for the rate limit window to reset, then retry with backoff. See the rate limits guide.
    DUPLICATE_REQUEST_IN_PROGRESS409 ConflictAnother request with this idempotency key is still being processed.Wait for the first request to finish. Reuse the same key; see email send retries.
    IDEMPOTENCY_PAYLOAD_MISMATCH409 ConflictThe idempotency key was previously used with a different request payload.Retry with the original payload or use a new key for a genuinely new send. See email send retries.
    RECIPIENT_DELIVERY_PENDING503 Service UnavailableOne or more recipients remain pending and can be resumed with the same idempotency key.Reuse the same idempotency key to resume remaining recipients.
    DELIVERY_AMBIGUOUS502 Bad Gateway or 503 Service UnavailableSimply Send could not confirm provider acceptance for one or more recipients or for the staged submission.If Simply Send already accepted the message for retry, wait for that result. Otherwise, reuse the same idempotency key if you retry. Check Email Events and the retry guide before resending.
    EMAIL_SIZE_APPROVAL_REQUIRED403 ForbiddenThe requested transactional email size requires workspace approval.Request a size increase under Account → Approvals, or reduce the message size.
    EMAIL_SIZE_APPROVAL_LIMIT_EXCEEDED403 ForbiddenThe requested email size is above the workspace’s approved size limit.Request a size increase under Account → Approvals, or reduce the message size.
    QUOTA_EXCEEDED429 Too Many RequestsThe workspace has reached a resource-creation quota.Review current and limit values under Account → Limits. Remove unused resources or contact support about plan limits.
    RECIPIENT_NOT_VERIFIED400 Bad RequestThe recipient address or domain did not pass the required verification check.Check your sending domains under Domains and follow the domain verification guide.
    FROM_DOMAIN_NOT_VALID400 Bad RequestThe sender domain is not verified or is not eligible for sending.Check your sending domains under Domains and follow the domain verification guide.
    SEND_FAILED500 Internal Server ErrorThe delivery provider rejected the message or all recipient attempts failed.Check Email Events before retrying. If no accepted send is recorded, retry using the same key. If the error persists, contact support with the request ID and timestamp.
    ENQUEUE_ERROR500 Internal Server ErrorThe service could not place the marketing message onto its processing queue.Check Email Events before retrying. If no accepted send is recorded, retry using the same key. If the error persists, contact support with the request ID and timestamp.
    SENT_ITEM_STORAGE_ERROR500 Internal Server ErrorThe service could not save the marketing message in the Sent folder.Check Email Events before retrying. If no accepted send is recorded, retry using the same key. If the error persists, contact support with the request ID and timestamp.
    COMPLIANCE_TEMPLATE_ERROR400 Bad RequestThe service could not load or apply the required compliance template.Check Email Events before retrying. If no accepted send is recorded, retry using the same key. If the error persists, contact support with the request ID and timestamp.
    CREDIT_POSTING_PENDING503 Service UnavailableDelivery completed or progressed, but credit usage could not yet be posted.Check Email Events before retrying. If no accepted send is recorded, retry using the same key. If the error persists, contact support with the request ID and timestamp.
    INTERNAL_ERROR500 Internal Server ErrorAn unexpected internal error prevented the request from completing.Check Email Events before retrying. If no accepted send is recorded, retry using the same key. If the error persists, contact support with the request ID and timestamp.
    PREVIEW_TIMEOUT503 Service UnavailableCampaign preview generation exceeded its time limit; the response confirms that no email was sent.Reduce the number of recipients or template size and retry. A preview timeout response indicates no email was sent.
    PREVIEW_TOO_LARGE400 Bad RequestThe rendered campaign preview exceeds the maximum preview size.Reduce the number of recipients or template size and retry. A preview timeout response indicates no email was sent.

    Web Setup and deliverability codes

    Resource APIs include domains, contacts, subscription groups, subscriptions, templates, compliance templates, webhooks, and deliverability. Their structured envelope uses error.code. Each code has its own row; read the endpoint’s error message for request-specific details.

    Error codeHTTP statusWhat it meansWhat to do
    INVALID_API_KEY401 UnauthorizedThe API Gateway request did not include an authenticated API key identity.Check the X-Api-Key value and use an active Web Setup key from the region’s API Keys page.
    API_KEY_UNAUTHORIZED403 ForbiddenThe key is inactive, is not a Web Setup key, or is not associated with a workspace.Create or activate a Web Setup key on API Keys and use it for this endpoint.
    WORKSPACE_UNAVAILABLE403 ForbiddenThe workspace associated with this key is missing or unavailable.Check the key/workspace association under Account → Workspaces. Contact support if the workspace should be active.
    WORKSPACE_MISMATCH403 ForbiddenThe optional X-Id value does not match the key’s workspace account ID.Use the account ID associated with the key on API Keys or omit X-Id.
    ROLE_UNAVAILABLE403 ForbiddenThe assigned role is missing, inactive, or not valid for Web Setup API keys.Assign an active role under Account → Workspaces, or create a key with a valid role on API Keys.
    PERMISSION_DENIED403 ForbiddenThe API key’s effective permissions do not include the required operation.Use a key with the required permission or ask a workspace administrator to update its role in Account → Workspaces. See the workspace guide.
    ACCESS_DENIED403 ForbiddenThe requested webhook or resource operation is not allowed for this workspace or principal.Use a key with the required permission or ask a workspace administrator to update its role in Account → Workspaces. See the workspace guide.
    FORBIDDEN403 ForbiddenThe caller does not have access to this operation or resource.Use a key with the required permission or ask a workspace administrator to update its role in Account → Workspaces. See the workspace guide.
    INVALID_ARGUMENT400 Bad RequestOne or more API arguments failed validation.Follow the endpoint’s parameter description and correct the named input. Browse the API reference for the endpoint.
    INVALID_PARAMETER400 Bad RequestA parameter or resource-specific input failed validation.Follow the endpoint’s parameter description and correct the named input. Browse the API reference for the endpoint.
    INVALID_REQUEST400 Bad RequestThe request does not match the expected endpoint contract.Follow the endpoint’s parameter description and correct the named input. Browse the API reference for the endpoint.
    BAD_REQUEST400 Bad RequestThe endpoint could not process the request as submitted.Follow the endpoint’s parameter description and correct the named input. Browse the API reference for the endpoint.
    MISSING_PARAMETER400 Bad RequestA required endpoint parameter or resource identifier was omitted.Follow the endpoint’s parameter description and correct the named input. Browse the API reference for the endpoint.
    MISSING_REQUIRED_FIELD400 Bad RequestA required field is missing from the request body.Follow the endpoint’s parameter description and correct the named input. Browse the API reference for the endpoint.
    CONFLICT409 ConflictThe request conflicts with the current state of the resource, such as a domain group name that already exists.Read the response message and check existing domain groups under Domains. Choose a different name or use the existing group, then retry.
    INVALID_CONTACT400 Bad RequestThe contact data does not satisfy contact validation rules.Check the accepted identifier, fields, filters, and version in the Contacts API. Refresh a contact after a conflict, then retry with the current value.
    INVALID_CONTACT_ID400 Bad RequestThe supplied contact ID is not valid.Check the accepted identifier, fields, filters, and version in the Contacts API. Refresh a contact after a conflict, then retry with the current value.
    INVALID_CONTACT_IDS400 Bad RequestOne or more contact IDs in the request are invalid.Check the accepted identifier, fields, filters, and version in the Contacts API. Refresh a contact after a conflict, then retry with the current value.
    INVALID_CONTACT_UPDATE400 Bad RequestThe requested contact changes contain invalid fields or values.Check the accepted identifier, fields, filters, and version in the Contacts API. Refresh a contact after a conflict, then retry with the current value.
    CONTACT_UPDATE_CONFLICT409 ConflictThe contact changed while this update was being applied.Check the accepted identifier, fields, filters, and version in the Contacts API. Refresh a contact after a conflict, then retry with the current value.
    UNSUPPORTED_FILTER400 Bad RequestThe endpoint does not support the requested filter.Check the accepted identifier, fields, filters, and version in the Contacts API. Refresh a contact after a conflict, then retry with the current value.
    UNSUPPORTED_VERSION400 Bad RequestThe requested API version or version value is not supported.Check the accepted identifier, fields, filters, and version in the Contacts API. Refresh a contact after a conflict, then retry with the current value.
    NOT_FOUND404 Not FoundThe requested resource does not exist in this workspace.Check the path and resource ID in the matching API reference. Confirm the resource belongs to the workspace selected by the key.
    ROUTE_NOT_FOUND404 Not FoundThe requested API route is not available.Check the path and resource ID in the matching API reference. Confirm the resource belongs to the workspace selected by the key.
    TEMPLATE_NOT_FOUND404 Not FoundThe specified email template does not exist in this workspace.Check the path and resource ID in the matching API reference. Confirm the resource belongs to the workspace selected by the key.
    SEGMENT_NOT_FOUND404 Not FoundThe specified contact segment does not exist or is not available.Check the path and resource ID in the matching API reference. Confirm the resource belongs to the workspace selected by the key.
    GROUP_NOT_FOUND404 Not FoundThe specified subscription group does not exist in this workspace.Check the path and resource ID in the matching API reference. Confirm the resource belongs to the workspace selected by the key.
    CONTACT_NOT_FOUND404 Not FoundThe specified contact does not exist in this workspace.Check the path and resource ID in the matching API reference. Confirm the resource belongs to the workspace selected by the key.
    MEMBER_NOT_FOUND404 Not FoundThe specified subscription-group member does not exist.Check the path and resource ID in the matching API reference. Confirm the resource belongs to the workspace selected by the key.
    LIST_NOT_FOUND404 Not FoundThe specified contact list does not exist in this workspace.Check the path and resource ID in the matching API reference. Confirm the resource belongs to the workspace selected by the key.
    INVALID_TEMPLATE_INPUT400 Bad RequestThe template request has invalid or unsupported input.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    INVALID_FIELD400 Bad RequestA template field has an invalid value or format.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    INVALID_FIELDS400 Bad RequestOne or more supplied fields are not allowed for this template operation.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    INVALID_HTML_CONTENT400 Bad RequestThe template HTML is invalid or violates template-content validation.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    INVALID_TYPE400 Bad RequestThe requested template type is not supported for this operation.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    INVALID_DEFAULT_FLAG400 Bad RequestThe default-template flag has an invalid value or state.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    NO_FIELDS_TO_UPDATE400 Bad RequestThe update request contains no supported fields to change.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    TEMPLATE_LOCKED409 ConflictThe template is locked and cannot be changed or deleted in its current state.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    TEMPLATE_NOT_APPROVED400 Bad RequestThe template has not completed the required approval step.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    TEMPLATE_APPROVAL_CONFLICT409 ConflictThe template changed while approval was being applied.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    CANNOT_DELETE_DEFAULT400 Bad RequestThe default compliance template cannot be deleted.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    COMPLIANCE_TEMPLATE_NOT_FOUND404 Not FoundThe requested compliance template does not exist.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    INVALID_COMPLIANCE_TEMPLATE_TYPE400 Bad RequestThe selected compliance template has the wrong type for this operation.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    COMPLIANCE_TEMPLATE_NOT_APPROVED400 Bad RequestThe selected compliance template has not been approved.Correct the field guidance and complete any required approval. See Templates or Compliance Templates.
    DOMAIN_CONFLICT409 ConflictThe domain conflicts with a domain or identity already registered in this account.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    DOMAIN_NOT_AVAILABLE400 Bad RequestThe domain cannot be registered for this workspace or region.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    DOMAIN_NOT_ACTIVE400 Bad RequestThe domain is not active for the requested operation.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    DOMAIN_NOT_VERIFIED409 ConflictThe domain has not passed ownership verification.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    DNS_RECORDS_NOT_READY400 Bad RequestThe required DNS records are missing or have not propagated yet.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    INVALID_DOMAIN_FORMAT400 Bad RequestThe domain name is not in a supported format.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    INVALID_USE_CASE400 Bad RequestThe selected domain use case is invalid or not available.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    INVALID_DKIM_KEY_TYPE400 Bad RequestThe selected DKIM key type is not supported.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    DOMAIN_AUTHORITY_ACKNOWLEDGEMENT_REQUIRED400 Bad RequestThe domain ownership or authority acknowledgement is missing.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    DOMAIN_ALREADY_VERIFIED409 ConflictThe domain is already verified; no further verification action is needed.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    MISSING_DOMAIN_ID400 Bad RequestThe request does not include the required domain ID.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    DOMAIN_NOT_FOUND404 Not FoundThe specified domain does not exist in this workspace.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    SANDBOX_PARENT_WORKSPACE_REQUIRED400 Bad RequestA sandbox domain operation requires its parent workspace to be specified.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    SANDBOX_PARENT_WORKSPACE_INVALID400 Bad RequestThe supplied parent workspace is not a valid live workspace for this sandbox.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    SANDBOX_DOMAIN_MUST_BE_PARENT_SUBDOMAIN400 Bad RequestA sandbox domain must be a subdomain of the parent workspace domain.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    PAID_PLAN_REQUIRED403 ForbiddenThis domain feature is available only with an eligible paid plan.Check the domain under Domains, correct its DNS, use case, DKIM type, and required acknowledgements, then follow the domain verification guide. Sandbox domains must meet the parent-workspace rules.
    GET_DNS_RECORDS_FAILED400 / 403 / 404The API could not retrieve records for the specified domain.Check the domain ID and workspace on Domains, then retry the DNS records request.
    DELETE_DOMAIN_FAILED403 / 404The API could not delete the specified domain in the current workspace.Confirm the domain ID and workspace on Domains, then retry the delete request.
    VERIFY_DOMAIN_FAILED403 / 404The API could not verify the specified domain in the current workspace.Check the domain ID and workspace on Domains. Follow the domain verification instructions and contact support if the error continues.
    ASSIGN_DOMAIN_FAILED400 / 403 / 404The domain could not be assigned to the requested group.Check that the domain and group IDs belong to this workspace on Domains, then retry the assignment.
    ALREADY_MEMBER409 ConflictThe contact is already a member of the subscription group.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    AMBIGUOUS_SUBSCRIBER409 ConflictThe lookup matched multiple subscribers and needs a more specific identifier.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    INVALID_SUBSCRIBER_LOOKUP400 Bad RequestThe subscriber lookup must include a supported member key, contact ID and email, or email.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    INVALID_SUBSCRIPTION_ID400 Bad RequestThe supplied subscription membership ID is not valid.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    IS_ACTIVE_REQUIRED400 Bad RequestThe update must specify a boolean isActive value.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    MEMBER_KEY_MISMATCH400 Bad RequestThe member key does not match the contact and email supplied for this subscription.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    MEMBERSHIP_NOT_ALLOWED409 ConflictThe contact, email point, or group capacity no longer permits this membership change.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    EMAIL_NOT_ON_CONTACT400 Bad RequestThe email address is not associated with the specified contact.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    EMAIL_SUPPRESSED409 ConflictThe email address is suppressed for the workspace or subscription group.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    VERIFICATION_REQUIRED409 ConflictThe group requires a verified confirmation flow before adding this member.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    RECONSENT_REQUIRED409 ConflictA previously unsubscribed member cannot be reactivated without a verified opt-in flow.Use the correct contact and group identifiers and a supported consent method. Complete verified opt-in before adding or reactivating membership; see the double opt-in guide and Subscriptions API.
    LIST_ALREADY_EXISTS409 ConflictA list with the same unique name or configuration already exists.Check existing lists at Subscription Groups or domain groups under Domains. Preserve default groups and check the group ID before retrying.
    DEFAULT_LIST_DELETION_NOT_ALLOWED409 ConflictThe default list is protected and cannot be deleted.Check existing lists at Subscription Groups or domain groups under Domains. Preserve default groups and check the group ID before retrying.
    DELETE_GROUP_FAILED400 / 404The service could not delete the requested subscription group.Check existing lists at Subscription Groups or domain groups under Domains. Preserve default groups and check the group ID before retrying.
    QUOTA_EXCEEDED429 Too Many RequestsThe workspace has reached the quota for creating this resource.Use the current/limit details in the response and review Account → Limits. Remove unused resources or contact support about plan limits.
    INTERNAL_ERROR500 Internal Server ErrorAn unexpected service or dependency error occurred.Retry safe reads with backoff. For writes, check whether the resource was created or updated before retrying. Contact support if it continues.

    Retrying email safely

    Use the same Idempotency-Key and unchanged payload when recovering from a send timeout, an in-progress response, or a pending recipient result. Check Email Events before making a new send. A new key means a new operation and may send a duplicate. See Email send retries for managed retry behavior.

    When to contact support

    Contact Simply Send support when a 5xx or dependency error continues, your key/workspace/plan appears correct but access is denied, a domain or size approval state is unexpected, or a send remains ambiguous. Include the region, UTC timestamp, HTTP status, request ID if present, endpoint, and response body. Never include API keys or message content.