List event logs in Apideck Webhook
A documented Apideck Webhook 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
List event logs
- GETReads data · Webhooks
unify.apideck.com/webhook/logs
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 Apideck Webhook 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 Apideck Webhook operations
- Create webhook subscriptionPOST · changes data
- Delete webhook subscriptionDELETE · changes data
- Update webhook subscriptionPATCH · changes data
- Resolve and Execute a connection webhookPOST · changes data
- Execute a webhookPOST · changes data
- Execute a webhookPOST · changes data
- List webhook subscriptionsGET · reads data
- Get webhook subscriptionGET · reads data
Questions
- Can HumDay list event logs in Apideck Webhook?
- Yes. This operation is published in Apideck Webhook'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 Apideck Webhook account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Apideck Webhook.
- 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 Apideck Webhook account.
Where this came from
Read from a published API description for Apideck Webhook at raw.githubusercontent.com/apideck-libraries/openapi-specs/master/webhook.yml. The description above is the provider’s own wording, not ours. Last published 2023-04-19.