Tripletex
Idempotency key
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
We are currently taking this in to consideration and are doing the preliminary discussions & exploratory work to see if this is something that could be added in a practical way.
Can't say anything about if / when this would be implemented but if / when it gets implemented we will notify you via this issue.
@stianjensen, fyi: we are using externalVoucherNumber for this purpose, and during retry we first check if voucher with this external number already exists before posting again. And I agree that proper idempotency header is needed.
Hey! We are implementing an integration with tripletex, and was looking into idempotency when I found this issue. Just checking if this is something that has been addressed?
