Tripletex / Tripletex/tripletex-api2
Idempotency key
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 49
- Forks
- 47
- Avg merge
- 1h 1m
- Merged PRs (30d)
- 1
Description
Hi!
Not sure if this is the correct forum for feature requests in the API or just the documentation, but here goes anyway!
It would be great if all request could take an optional idempotency key header, to ensure that resources are not created as duplicates when performing retries on network requests.
We often sync a lot of invoices and payments from our system in to Tripletex, and some times a network request will fail, but we don't know if only the response delivery back to us failed, or if the resource was not created at all. Trying to sync the same resource again could result in it being created twice in Tripletex, which is not good.
Stripe has this feature in their API, for reference: https://stripe.com/docs/api/idempotent_requests
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an implementation entry point. Start by reviewing the API resources and examples in this repository and determine where request headers and retry behavior are defined; done should include a decided scope for optional idempotency-key handling across requests and documented duplicate-prevention behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100