#mathiasm8
1 messages · Page 1 of 1 (latest)
that is an approach we recommend yes; your endpoint should be idempotent and be able to 'infer' creation of an object on an updated event by just calling whatever code you would have called, if it's an object you haven't seen yet
An is the "read-after-write" warning only aplicaple to the search API? I mean if one of my users signs up for a subscription a lot of webhooks and data are being processed. Can I be sure that the API endpoints I will call in this case is updated immediately with that data?
not sure I follow, could you re-state it?
https://stripe.com/docs/search here you state that:
Don’t use search for read-after-write flows (for example, searching immediately after a charge is made) because the data won’t be immediately available to search. Under normal operating conditions, data is searchable in under 1 minute. Propagation of new or updated data could be more delayed during an outage.
Is this also the same for calling any other endpoint or is it only search?
that's specific to the Search API