Skip to main content
Error format Every error is an application/problem+json body (RFC 9457) with a stable code. Handle errors by code; the detail text can change.
Field definitions
  • code – A stable identifier for the error, in the format TED-NNNN.
  • title – A short summary of the problem type.
  • status – The HTTP status code.
  • detail – A human-readable explanation of this occurrence.
  • type – A reference to the problem type. Defaults to about:blank.
  • instance – Optional. A reference to this occurrence.
  • errors – Optional. One entry for each rejected field, with location, message and value.
  • upstream – Optional. The error that a proxied provider reported, with its own code and message, verbatim.
Every response, success or error, carries the X-Request-Id header. Include it in support requests.

TED Lerian errors


The following errors can occur when you call the TED Lerian endpoints. TED-0031, TED-1011 and TED-1013 are never error responses: they arrive in rejection.code of a transfer in status REJECTED. On a send, TED-1001 arrives the same way. If you retry a POST /v1/transfers whose first attempt got no answer, any refusal can still mean that the first attempt created the transfer: look it up with GET /v1/transfers before you send it with a new key.