Managed Contact Delete in Linode
A documented Linode 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
Managed Contact Delete
- DELETEChanges data · Managed
api.linode.com/managed/contacts/{contactId}
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 Linode 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 Linode operations
- Managed Contact CreatePOST · changes data
- New Tag CreatePOST · changes data
- Domain Record CreatePOST · changes data
- Support Ticket OpenPOST · changes data
- Payment MakePOST · changes data
- Payment Method AddPOST · changes data
- Reply CreatePOST · changes data
- Support Ticket Attachment CreatePOST · changes data
Questions
- Can HumDay managed contact delete in Linode?
- Yes. This operation is published in Linode'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 Linode data?
- Yes — this is a DELETE operation, so it changes something in Linode. 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 Linode account.
Where this came from
Read from a published API description for Linode at www.linode.com/docs/api/openapi.yaml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.