Remove an existing segment in Resend
A documented Resend 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
Remove an existing segment
- DELETEChanges data · Segments
api.resend.com/segments/{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 Resend 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 Resend operations
- Create a new contactPOST · changes data
- Send an emailPOST · changes data
- Create an eventPOST · changes data
- Create a new webhookPOST · changes data
- Create a new contact propertyPOST · changes data
- Send an eventPOST · changes data
- Remove an existing contact by ID or emailDELETE · changes data
- Update a single contact by ID or emailPATCH · changes data
Questions
- Can HumDay remove an existing segment in Resend?
- Yes. This operation is published in Resend'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 Resend data?
- Yes — this is a DELETE operation, so it changes something in Resend. 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 Resend account.
Where this came from
Read from the API description Resend publishes themselves at resend.com/openapi.json. The description above is the provider’s own wording, not ours.