generated: '2026-08-12'
method: searched
source: https://products.zetaglobal.com/sailthru/Content/developers/api-basics/responses.html
docs: https://products.zetaglobal.com/sailthru/Content/developers/api-basics/responses.html
api: sailthru:sailthru-api
format: proprietary
rfc9457: false
envelope:
  fields: [error, errormsg]
  description: >-
    On failure the response body carries a numeric `error` field and a human
    (technical) `errormsg` string, in whichever serialization the `format`
    parameter requested. The docs explicitly warn that errormsg is technical
    and should not be surfaced to end users. There is no `type` URI, no
    `title`/`detail` split and no application/problem+json media type, so this
    is a pre-RFC-9457 error registry rather than Problem Details.
  observed_example: >-
    GET https://api.sailthru.com/send with no credentials returns HTTP 400 and
    <?xml version="1.0" encoding="utf-8"?><triggermail><error>2</error>
    <errormsg>Missing required parameter: api_key</errormsg></triggermail>
  observed: '2026-08-12'
http_statuses:
- {status: 200, meaning: Success}
- {status: 400, meaning: The request cannot be fulfilled due to bad syntax or an invalid parameter}
- {status: 401, meaning: Invalid authentication credentials — for example a request with an invalid API key}
- {status: 403, meaning: Valid request but it has been rejected by the server}
- {status: 404, meaning: 'Resource was not found — for example, a request to get a blast that does not exist'}
- {status: 405, meaning: A request was made of a resource using a request method not supported by that resource}
- {status: 409, meaning: The request cannot be completed because it conflicts with an established ruleset}
- {status: 429, meaning: Exceeded the limit of requests per minute for the given type (GET or POST) and endpoint}
- {status: 500, meaning: Something is broken on the system's side}
errors:
- {code: 1, message: Unsupported HTTPS method, class: request}
- {code: 2, message: Missing HTTPS GET/POST parameter, class: request}
- {code: 3, message: Invalid API key, class: auth}
- {code: 4, message: Disallowed IP, class: auth}
- {code: 5, message: Authentication failed, class: auth}
- {code: 6, message: Invalid UTF-8 characters for field, class: request}
- {code: 9, message: Internal Error, class: server}
- {code: 11, message: Invalid Email, class: validation}
- {code: 12, message: Unknown send_id, class: not-found}
- {code: 13, message: Unknown blast_id, class: not-found}
- {code: 14, message: Unknown template, class: not-found}
- {code: 15, message: Unknown list, class: not-found}
- {code: 16, message: Unknown site, class: not-found}
- {code: 17, message: Login failure, class: auth}
- {code: 18, message: Invalid time, class: validation}
- {code: 21, message: You must be approved to email, class: entitlement}
- {code: 22, message: You must be a Premium client to use this API call, class: entitlement}
- {code: 32, message: Email has opted out of delivery from client, class: suppression}
- {code: 33, message: Email has opted out of delivery from template, class: suppression}
- {code: 34, message: Email may not be emailed, class: suppression}
- {code: 35, message: Email is a known hardbounce, class: suppression}
- {code: 36, message: Unverified from email, class: entitlement}
- {code: 37, message: Email will only accept basic templates, class: suppression}
- {code: 41, message: Unable to delete, already sent, class: conflict}
- {code: 42, message: 'Invalid UTF-8 characters for field: [field name]', class: validation}
- {code: 43, message: 'Too many [type] requests this minute to /[endpoint] API', class: rate-limit}
- {code: 99, message: Other error, class: server}
- {code: XX, message: Unable To Stream, class: server}
error_count: 28