-
Notifications
You must be signed in to change notification settings - Fork 0
Waytostay
Waytostay has a lot of good properties that generated more bookings than other partners at the time of writing.
We implement the Waytostay Api Version 4.
Rate limits are applied and HTTP Status 429 is returned if we're being limited.
Official documentation:
- Booking Horizon (One and the same as waytostay)
- Sandbox live doc and playground
- Production live doc and playground
OAuth 2.0 is the authentication method. client_id
and client_secret
for test and production environments are the same, only the base_url
is different; base_url
is the same as the live documentation links above.
For deployment we need to set the following ENV:
- WAYTOSTAY_URL="https://apis.waytostay.com"
- WAYTOSTAY_TOKEN_URL="/oauth"
- WAYTOSTAY_CLIENT_ID=xxx
- WAYTOSTAY_CLIENT_SECRET=xxx
See POST /bookings/quote
at the documentations docx NOTE: This seem to be outdated, quotation response fields are different from what we get in sandbox environment. When in doubt, just follow sandbox.
There're also documentation found in html or playground
Concierge creates and immediately confirm new bookings, since we assume payment is collected beforehand. The following flow is suggested by waytostay:
See POST /bookings
and POST /bookings/:ref/confirmation
at the documentations(docx or html) or playground