#mad-idempotency
1 messages · Page 1 of 1 (latest)
Sorry, please allow me to correct, it does contain the key in the request: https://stripe.com/docs/api/events/object#event_object-request
This property is populated for events on or after May 23, 2017.
i'm confused 🙂
Is there anything I can help with your use case?
they say that it's only populated for event after 2017, so it should be present
ohh i've just read that it's related to the request that generated it
what about the case of a webhook ?
my use case is trying to handle this https://stripe.com/docs/webhooks/best-practices#duplicate-events
The webhook event with the id evt_xxxxx should contain the key, do you have an example event I could refer to please?
this one for ex: evt_1KGy4pBVFeaV0FZKbdmBJ94i
on this one its null
"request": {
"id": null,
"idempotency_key": null
}
this is interesting, please allow me look deeper into this
thank you @astral cargo
Hi @mellow comet, this is Jack from Stripe. this particular event is an automatic handling (subscription status from active to past_due) which it's not triggered by your API call, that's why both id and idempotency_key are null.