Delete a webhook in BulkSMS JSON
A documented BulkSMS JSON 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
Delete a webhook
- DELETEChanges data · Webhooks
api.bulksms.com/webhooks/{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 BulkSMS JSON 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 BulkSMS JSON operations
- Send MessagesPOST · changes data
- Create a webhookPOST · changes data
- Create a blocked numberPOST · changes data
- Upload an attachment via a signed URLPOST · changes data
- Update a webhookPOST · changes data
- Transfer credits to another accountPOST · changes data
- Send message by simple GET or POSTGET · reads data
- Retrieve MessagesGET · reads data
Questions
- Can HumDay delete a webhook in BulkSMS JSON?
- Yes. This operation is published in BulkSMS JSON'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 BulkSMS JSON data?
- Yes — this is a DELETE operation, so it changes something in BulkSMS JSON. 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 BulkSMS JSON account.
Where this came from
Read from a published API description for BulkSMS JSON at developer.bulksms.com/json/v1/swagger.yaml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.