Display conversation details in reverb
A documented reverb operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Display conversation details with messages in natural time order (oldest to newest)
- GETReads data · my
api.reverb.com/my/conversations/{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 reverb operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
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 display conversation details 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.
- Does this change anything in my reverb account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in reverb.
- 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.