Skip to content

Idempotency key for expensive POST requests #618

@kartpop

Description

@kartpop

Is your feature request related to a problem? Please describe.
Clients retrying POST actions is bad especially when it's expensive like in documents.

Describe the solution you'd like
To overcome processing expensive duplicate requests, we can introduce an idempotency_key in requests which clients can use to retry. This idempotency_key needs to be stored against the relevant entity, so when users/clients retries creating the same entity, entity creation can be skipped and the API can just return the already existing entity.

Additional context
See Stripe's API docs - https://docs.stripe.com/api/idempotent_requests

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions