Connect reverb and Viator Documentation & Specification Merchant Partners
Describe what you want to happen between reverb and Viator Documentation & Specification Merchant Partners in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
reverb
163 documented operations. See all reverb operations
- POSTCreate a new address in your address book
/my/addresses - POSTAdd feedback about an order's buyer
/orders/{order_id}/feedback/buyer - POSTAdd feedback about an order's seller
/orders/{order_id}/feedback/seller - POSTSend a message
/my/conversations/{conversation_id}/messages - POSTCreate a listing
/listings - POSTRegister a webhook
/webhooks/registrations
Viator Documentation & Specification Merchant Partners
27 documented operations. See all Viator Documentation & Specification Merchant Partners operations
- POST/search/freetext
/search/freetext - POST/search/products
/search/products - POST/booking/status/items
/booking/status/items - POST/search/products/codes
/search/products/codes - POST/booking/book
/booking/book - POST/booking/status
/booking/status
How a reverb and Viator Documentation & Specification Merchant Partners automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in reverb and Viator Documentation & Specification Merchant Partners, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- OData for namespace microsoft.graph and reverb11,575 operations
- OData for namespace microsoft.graph and Viator Documentation & Specification Merchant Partners11,439 operations
- Cloudflare and reverb3,285 operations
- Cloudflare and Viator Documentation & Specification Merchant Partners3,149 operations
- NetBox and reverb1,007 operations
- NetBox and Viator Documentation & Specification Merchant Partners871 operations
- GitHub and reverb974 operations
- GitHub and Viator Documentation & Specification Merchant Partners838 operations
- Mist and reverb931 operations
- Mist and Viator Documentation & Specification Merchant Partners795 operations
Questions about connecting reverb and Viator Documentation & Specification Merchant Partners
- Can reverb connect with Viator Documentation & Specification Merchant Partners?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect reverb to Viator Documentation & Specification Merchant Partners?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate reverb and Viator Documentation & Specification Merchant Partners?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across reverb and Viator Documentation & Specification Merchant Partners?
- reverb publishes 163 documented operations and Viator Documentation & Specification Merchant Partners publishes 27. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either reverb or Viator Documentation & Specification Merchant Partners is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for reverb and Viator Documentation & Specification Merchant Partners. Descriptions are each provider’s own words, not ours.