Remove a webhook by id in ZEIT

What this operation does

Remove a webhook by id

• DELETEChanges data · webhooksapi.zeit.co/v1/integrations/webhooks/:id

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which ZEIT operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other ZEIT operations

• Create a new webhookPOST · changes data
• Gets a list of domains registered for the authenticating userGET · reads data
• Get a list of existent webhooksGET · reads data
• Get a domain for the authenticated user by nameGET · reads data

All 5 ZEIT operations

Questions

Can HumDay remove a webhook by id in ZEIT?

Yes. This operation is published in ZEIT's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my ZEIT data?

Yes — this is a DELETE operation, so it changes something in ZEIT. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

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 ZEIT account.

Where this came from

Read from a published API description for ZEIT at unpkg.com/@zeit/openapi. The description above is the provider’s own wording, not ours. Last published 2021-06-21.