Idempotency-Key conflict
| HTTP status | 422 |
| Type | https://docs.investorliftdata.com/errors/idempotency-key-conflict |
| Retryable | No |
| Retry-After header | No |
What the body says
The response body says:
The Idempotency-Key on this request was already used for a request with a different body, so it cannot be replayed. Nothing was charged. Send the request again with a new Idempotency-Key.
What happened to the Credits
No Credits are consumed by a call that ends here.
Retrying
Not retryable. Sending the same request again returns the same error. Change the request as the detail directs before sending it again.
Body members
None. The body carries exactly the base members: type, title, detail, status and trace_id.
Retry-After
No. This response carries no Retry-After header.
Every error response is an RFC 9457 Problem Detail sent as application/problem+json,
and every response carries a trace-id header, repeated in the body as trace_id.
The Trace ID is the only handle support needs to find your call.