HumDay

/health/check in Viator Documentation & Specification Merchant Partners

A documented Viator Documentation & Specification Merchant Partners operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.

Automate this

What this operation does

/health/check

  • GETReads data · General servicesviatorapi.viator.com/health/check

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Viator Documentation & Specification Merchant Partners operations the program may use, and this is one of them.
  3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Viator Documentation & Specification Merchant Partners operations

All 27 Viator Documentation & Specification Merchant Partners operations

Questions

Can HumDay /health/check in Viator Documentation & Specification Merchant Partners?
Yes. This operation is published in Viator Documentation & Specification Merchant Partners'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 Viator Documentation & Specification Merchant Partners account?
No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Viator Documentation & Specification Merchant Partners.
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 Viator Documentation & Specification Merchant Partners account.

Where this came from

Read from a published API description for Viator Documentation & Specification Merchant Partners at api.apis.guru/v2/specs/viator.com/1.0.0/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-06-10.

We use cookies to measure how the site is used.