HolidaySG has opened its Partner API to approved B2B partners. Through one base address, one authentication scheme and one response format, a travel business can sell attractions and tours, hotels, HolidaySG eSIM data plans and ferry tickets, with visa processing handled with our team on request. Every API starts on a sandbox key that works at once, and a live key follows after HolidaySG has reviewed the integration.
What the Partner API covers
The Partner API is a REST interface served from a single base address. Partners call it from their own servers to search inventory, check availability, lock a price, book, read bookings back and cancel, then reconcile the result against a statement. Answers are JSON in one common envelope with the data, a request identifier and a list of errors, so the same client code can read every service.
Four services are open to partners, and each has its own release with the detail of its endpoints.
- Attractions and tours: catalogue, live availability by date, price-locked quotes, signed bookings, cancellations, statements and webhooks. An OCTO-compatible endpoint is available for resellers that already speak that open standard.
- Hotels: destination search, every bookable rate for the dates, quotes, signed bookings and cancellation requests, with the hotel's own rules and the cancellation deadline returned for each rate.
- HolidaySG eSIM: countries, regions and plans, orders with safe retries, install details, usage, top-ups, statements and webhooks.
- Ferry: sectors, sailings, exact prices worked out on our server, bookings paid from the wallet, and cancellation requests handled by our team.
- Visa processing is not part of the API. Visa applications for partners are handled with our team; write to api@holidaysg.com with your destinations and volumes.
One account, one key per API
Access starts with an approved B2B partner account. Once the account is approved, the partner creates keys in the B2B portal under Staff and API keys, on the API users tab. Keys are issued per API, so an integration that only sells hotels never holds a key that can book ferries. Each API a key may use is stored as one supplier scope on that key, and a service the key has not been granted answers with an authorisation error rather than empty data.
Every key is locked to between one and three static server addresses. The list is typed in when the key is created, it can be edited later in the same place, and it can never be left empty. A call from any other address is refused. Addresses are matched exactly, and ranges are not accepted.
From sandbox to a live key
A sandbox key can be created straight from the portal and works at once. It behaves like production in everything a developer needs: the same endpoints, the same request signing, the same response shapes and the same error codes. What changes is the effect. Bookings are simulated and carry an SBX- reference, nothing is charged to the wallet, and nothing is reserved with a real supplier.
A live key is never created by the portal form. The path is deliberate and short.
- Apply for a B2B partner account at holidaysg.com/apply/b2b and, once approved, open Staff and API keys in the portal.
- Create a sandbox key for each API you want to test. There is one active sandbox key per API.
- Run your integration on the sandbox until the flow works end to end. Attractions have a checklist of seven calls, tracked automatically from your own requests; hotels, eSIM and ferry are switched on for your account after your own sandbox test.
- Press Request live key for that API. A HolidaySG administrator reviews the request, decides whether the key may book and cancel, and approves or declines it. You receive an e-mail with the decision.
- After approval, you create the live key yourself in the same place. HolidaySG never sees it, and the secret is shown once.
How requests are secured
Every call carries the API key in an X-Api-Key header. Calls that move money, which means bookings and cancellations, are also signed with an HMAC-SHA256 signature computed over the timestamp, method, path, a single-use nonce and the raw body, using a signing secret that belongs to the key. A signature must be fresh, within five minutes of server time, and a nonce cannot be replayed. A dry-run endpoint accepts a signed request with no side effects, so a partner can prove the signing code before any booking exists.
Bookings also need an Idempotency-Key header. Repeating the same booking with the same key returns the original booking and never charges the wallet twice.
- Scopes are strict: catalogue read, quote write, booking read, booking write, booking cancel and statement read.
- Keys can expire or be revoked, and the account behind a key must be an approved B2B account.
- Keys and secrets belong on the partner's server, never in browser or mobile code.
Paying, statements and webhooks
Amounts are in Singapore dollars. Partners fund a prepaid wallet by card in the portal; bookings debit the wallet and refunds return to it. Attractions and hotels can also be settled against an approved credit line, and ferry and eSIM are wallet only. Refunds are handled by people at HolidaySG and are never issued automatically.
Attractions and eSIM provide monthly statements for reconciliation. Booking updates are pushed to a partner endpoint, so nobody has to poll: the portal page for webhooks lets a partner save an HTTPS address and send a clearly marked test event before any real booking exists, and eSIM adds its own set of signed events.
Limits, versions and errors
Request limits apply per partner, and every response reports the remaining allowance. When a limit is hit the API answers with a retry-after header, and clients should honour it.
The version is part of the address, and an unsupported version is refused with a clear code. Errors always use the same envelope with a machine-readable code, so a partner can branch on the code instead of parsing text.
Documentation and support
The developer page at holidaysg.com/developers/b2b-api documents every service, with request and response samples, error catalogues and test scenarios for the sandbox. A machine-readable OpenAPI file lists every path, verb and scope for attractions, hotels, eSIM and ferry. Questions about the API go to api@holidaysg.com.
Frequently asked questions
Who can use the Partner API?
Approved B2B partners. Apply for a partner account at holidaysg.com/apply/b2b; after approval you create sandbox keys in the portal.
How quickly can I start testing?
A sandbox key is created in the portal and works at once, one per API, once you have given one to three static server addresses.
Can I create a live key myself?
Not directly. You request a live key for an API, a HolidaySG administrator reviews it, and after approval you create the key yourself. HolidaySG never sees the key.
Does a sandbox booking cost anything?
No. Sandbox bookings are simulated, carry an SBX- reference and never debit the wallet or reserve real inventory.
Can I call the API from a browser or an app?
No. Keys and secrets must stay on your server, and calls are accepted only from the addresses registered on the key.
Is visa processing in the API?
No. Visa applications for partners are handled with our team on request; write to api@holidaysg.com.
What happens if I retry a booking after a timeout?
Send the same idempotency key. You receive the original booking and the wallet is not charged twice.
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.