IDEMPOTENCY_RECORD_LOST

500 Internal Server Error · type api_error When it happens You retried with an Idempotency-Key whose original request started more than two minutes ago and never recorded a response, for example because the server stopped after doing the work but before saving the answer. We can’t replay a response we don’t have, and we won’t run the request again in case it already took effect. What to do Don’t retry with this key; it will keep failing. There’s no Retry-After.

POST /v1/quotes: create the quote again with a new key. A duplicate quote is harmless: nothing is sent to anyone, and it expires on its own.
POST /v1/quotes/{id}/hosted-link: call it again with a new key. That revokes whichever link is current and returns a fresh one.

See idempotency.

Example

500 Internal Server Error

{
  "error": {
    "type": "api_error",
    "code": "IDEMPOTENCY_RECORD_LOST",
    "message": "The original request with this Idempotency-Key may have completed, but its response was not recorded. Retrying with this key will not succeed. Check whether the original request took effect before sending it again with a new Idempotency-Key.",
    "param": "Idempotency-Key",
    "doc_url": "https://docs.bridgelinepf.com/errors#IDEMPOTENCY_RECORD_LOST",
    "request_id": "req_8fJ2kQ9xLm4TzW7nB3cY5pDv"
  }
}

See all error codes, or how to handle errors.

Overview

400 and 422: the request

401: the key

403: permission

404, 405 and 409

429 and 5xx

Example

​Example

Example