Idempotence

Certain endpoints support idempotent requests so that a given request can be safely retried without performing the same operation twice. For example, if a request to accept a transfer does not respond due to network issues, you can retry the request using the same idempotent ID to ensure that only one transfer is performed.

Endpoints that support idempotent requests have an optional x-l2f-idempotency-id header field that can be populated with a unique string using your method of choice (such as a v4 UUID).

If a request is valid, Rail will save the request indefinitely. If a subsequent request is received with the same idempotentId we will return the previously saved response for that idempotentId.