Delete an event in Cenit IO Specification

What this operation does

Delete an event

• DELETEChanges data · Data Eventcenit.io/setup/observer/{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 Cenit IO Specification 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 Cenit IO Specification operations

• Create or update a webhookPOST · changes data
• Create or update an eventPOST · changes data
• Create or update a flowPOST · changes data
• Create or update an schemaPOST · changes data
• Create or update a connectionPOST · changes data
• Create or update a data typePOST · changes data
• Create or update a namespacePOST · changes data
• Create or update an schedulerPOST · changes data

All 40 Cenit IO Specification operations

Questions

Can HumDay delete an event in Cenit IO Specification?

Yes. This operation is published in Cenit IO Specification'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 Cenit IO Specification data?

Yes — this is a DELETE operation, so it changes something in Cenit IO Specification. 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 Cenit IO Specification account.

Where this came from

Read from a published API description for Cenit IO Specification at cenit-io.github.io/openapi/swagger.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.