HolidaySG has opened its attractions and tours API to approved B2B partners. A partner can browse the catalogue, confirm live availability for a date, lock a price for fifteen minutes, make a signed booking from a prepaid wallet and cancel it, all through one REST interface. Resellers who already integrate with the OCTO open standard can use a second, OCTO-shaped endpoint with the same keys.
What partners can sell
The API exposes the HolidaySG bookable catalogue of attractions, tours and tickets in one normalised shape. Partners receive the fields they need to transact, which means names, locations, images, opening hours and a bookable flag, and they price everything through quotes rather than from catalogue figures. The "from" figure on a product is only an indicative guide and is not a quotable price.
Product images are returned as stable HolidaySG addresses that need no key. Partners should store them as given and not try to interpret them.
The booking flow in six calls
The recommended integration follows the order below. Each step has its own safeguards, so a partner can retry network failures without worrying about duplicates.
- List products with GET /products, filtered by country, city, category or bookable status, and page through results with a cursor.
- Check GET /products/{id}/availability for a date and party size to see which options and ticket types can be booked.
- Create a quote with POST /quotes using the ticket type identifiers returned by availability.
- Book with POST /bookings, signed and carrying an idempotency key, using the quote identifier and the customer details.
- Read the result with GET /bookings/{id}, or let a webhook tell you.
- Cancel with POST /bookings/{id}/cancel, signed, when a traveller changes plans.
Live availability and ticket types
Availability is read from the live source at the moment of the request, never from a cached flag. If the source cannot be reached, the API answers with a clear unavailable code and the partner retries shortly, so a stale "available" never reaches a customer.
Bookable ticket type identifiers are not on the product record. They come from the availability answer, under each option, together with minimum and maximum quantities and any time slots. Products that need traveller details also return the questions that must be answered, and a booking without those answers is refused before any money moves.
Quotes lock the price
A quote returns each line, the total in Singapore dollars and an expiry fifteen minutes ahead. The unit price is the all-in amount the partner pays, with the partner's own commission group already applied. Booking against an expired quote returns a clear quote-expired answer and moves no funds, and the partner simply asks for a new quote.
Booking safely from a wallet
A booking debits the prepaid wallet, reserves the tickets and confirms them. Because this moves money, the call must be signed and must carry an idempotency key. Repeating the same call returns the original booking, and a different request on the same key is refused.
Outcomes are explicit, so integrations can respond to each one:
- Confirmed: the booking is made and paid from the wallet.
- Pending confirmation: the booking is reserved and paid but the confirmation is still being verified. Do not retry; it is reconciled by HolidaySG.
- Insufficient funds: the wallet balance is too low and nothing is charged.
- Reserve failed: the tickets could not be reserved and nothing is charged.
- Confirm failed: the reservation was rejected at confirmation and the wallet is refunded in full.
Cancelling and refunds
A signed cancellation returns the refund to the partner wallet, and it is issued only once the cancellation has been confirmed. Cancelling a booking that is already cancelled returns the same result without a second refund. A booking that cannot be cancelled, for example after its cut-off, is refused and no funds move; an unconfirmed cancellation is flagged for reconciliation rather than refunded on a guess.
A sandbox with test products
On a sandbox key, six test products cover the cases a developer needs: a standard single-option product, one with several options, one that asks for traveller details, one with a capacity limit, one available on weekdays only, and one for triggering error codes. The reference describes ten mandatory test scenarios, including a happy path, an idempotent retry, an expired quote, insufficient funds, a mismatched idempotency key, missing traveller answers, signature errors, cancellation edge cases, authorisation errors and validation errors.
Progress is tracked from your own sandbox calls. A certification endpoint reports which of seven steps you have completed: authentication, catalogue, availability, quote, signature check, booking and cancellation. A live attractions key is requested once all seven have passed.
OCTO for resellers
Resellers that already use the OCTO open standard for tours and activities can connect to a separate OCTO endpoint. It authenticates with a bearer token drawn from the same key store, so one credential works for both interfaces, and it applies the same address allow-list and the same supplier and booking scopes.
It exposes the supplier record, products, availability and a two-phase booking: a hold, then a confirmation with a wallet or credit payment method, and a cancellation. A hold lasts thirty minutes and the booking moves through on hold, confirmed, cancelled or expired. A sandbox key simulates the hold and moves no money. The OCTO endpoint is a switch that HolidaySG controls, so ask the API team to enable it for your account.
Vouchers, webhooks and statements
Once a booking is confirmed, the e-ticket is delivered by e-mail to the customer on the booking, and the booking record can be read at any time. Booking changes are pushed to the partner's HTTPS address with a signed webhook, retried up to five times on failure and delivered at least once, so partners should de-duplicate on booking identifier and status. Monthly statements are available for the last thirty-six months and are the reference for reconciliation.
Frequently asked questions
Where do I find the ticket type identifiers?
In the availability answer, under each option. They are not on the product record, so always drive a quote from a live availability response.
Is the "from" figure on a product the price I pay?
No. It is indicative only. The real price comes from a quote, which locks it for fifteen minutes.
What if I never receive the booking answer?
Retry the same request with the same idempotency key. You receive the original booking and are not charged twice.
When is a cancellation refunded?
The wallet refund is issued only after the cancellation is confirmed. Bookings past their cut-off cannot be cancelled and no funds move.
How do I test without real tickets?
Use a sandbox key and the test products. Bookings are simulated, carry an SBX- reference and never debit the wallet.
Do I need a different key for OCTO?
No. The OCTO endpoint accepts your existing key as a bearer token, with the same address allow-list and scopes, once HolidaySG has enabled it.
How are tickets delivered?
The e-ticket is sent by e-mail to the customer on the booking, and the booking can also be read through the API.
About HolidaySG
HolidaySG.com is a Singapore travel platform for attractions and tours, visas, hotels, ferry tickets and eSIM plans, with a B2B portal and Partner API for travel businesses.
Media enquiries: contact us.