Delete a draft listing in reverb
A documented reverb 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 draft listing.
- DELETEChanges data · listings
api.reverb.com/listings/{slug}
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 reverb 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 reverb operations
- Create a new address in your address bookPOST · changes data
- Add feedback about an order's buyerPOST · changes data
- Add feedback about an order's sellerPOST · changes data
- Send a messagePOST · changes data
- Create a listingPOST · changes data
- Register a webhookPOST · changes data
- Unmark an item wantedDELETE · changes data
- Mark an item wanted. Returns 200 on success or 422 on failurePUT · changes data
Questions
- Can HumDay delete a draft listing in reverb?
- Yes. This operation is published in reverb'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 reverb data?
- Yes — this is a DELETE operation, so it changes something in reverb. 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 reverb account.
Where this came from
Read from a published API description for reverb at s3.amazonaws.com/swagger.reverb.com/swagger.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.