Delete a post in Trashnothing trash nothing
A documented Trashnothing trash nothing 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 post
- DELETEChanges data · posts
trashnothing.com/posts/{post_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 Trashnothing trash nothing 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 Trashnothing trash nothing operations
- Create an email alertPUT · changes data
- Save a post location for the current userPUT · changes data
- Send password reset emailPOST · changes data
- Submit a postPOST · changes data
- Reply to a postPOST · changes data
- Share a postPOST · changes data
- Update current userPUT · changes data
- Report a userPOST · changes data
Questions
- Can HumDay delete a post in Trashnothing trash nothing?
- Yes. This operation is published in Trashnothing trash nothing'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 Trashnothing trash nothing data?
- Yes — this is a DELETE operation, so it changes something in Trashnothing trash nothing. 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 Trashnothing trash nothing account.
Where this came from
Read from a published API description for Trashnothing trash nothing at trashnothing.com/api/trashnothing-openapi.yaml. The description above is the provider’s own wording, not ours. Last published 2023-03-03.