Deletes a Reactor rule in Ably Control
A documented Ably Control operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Deletes a Reactor rule
- DELETEChanges data · rules
control.ably.net/apps/{app_id}/rules/{rule_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 Ably Control operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Ably Control operations
- Updates app's APNs info from a.p12 filePOST · changes data
- Creates a keyPOST · changes data
- Creates a Reactor rulePOST · changes data
- Creates a queuePOST · changes data
- Creates a namespacePOST · changes data
- Creates an appPOST · changes data
- Deletes an appDELETE · changes data
- Updates an appPATCH · changes data
Questions
- Can HumDay deletes a reactor rule in Ably Control?
- Yes. This operation is published in Ably Control'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 Ably Control data?
- Yes — this is a DELETE operation, so it changes something in Ably Control. 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 Ably Control account.
Where this came from
Read from a published API description for Ably Control at raw.githubusercontent.com/ably/open-specs/main/definitions/control-v1.yaml. The description above is the provider’s own wording, not ours. Last published 2021-07-26.