Retrieves the details of an event in Stripe
A documented Stripe operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Retrieves the details of an event.
- GETReads data
api.stripe.com/v1/events/{id}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Stripe operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Stripe operations
- To upload a file to StripePOST · changes data
- This endpoint creates a draft invoice for a given customerPOST · changes data
- Creates a new customer objectPOST · changes data
- Creates an item to be added to a draft invoicePOST · changes data
- Creates a new subscription on an existing customerPOST · changes data
- Adds a new item to an existing subscriptionPOST · changes data
- Creates a new subscription schedule objectPOST · changes data
- To charge a credit card or other payment sourcePOST · changes data
Questions
- Can HumDay retrieves the details of an event in Stripe?
- Yes. This operation is published in Stripe's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Stripe account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Stripe.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Stripe account.
Where this came from
Read from a published API description for Stripe at raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.yaml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.