Loading
For agencies, OTAs and corporate buyers
Two surfaces over one inventory. Implement OCTO, or repoint an existing v2 distribution client and keep the code you already wrote. Settlement runs from a prefunded wallet with instant refunds.
Two contracts, one inventory
Both surfaces read the same availability and the same rates. Whichever you pick, you are looking at the operator's live inventory rather than a cached feed.
Open connectivity standard
A faithful implementation of the OCTO specification: supplier, product, option, unit, availability and booking, with the two-step reserve and confirm lifecycle the spec requires.
Drop-in compatible contract
Field-for-field compatible with the v2 contract many agencies have already integrated against. Change the base URL and your existing client keeps working.
Settlement
No card per booking. Prefund a balance, book against it, and let holds expire harmlessly when a client changes their mind.
Top up in any currency we support. We record what you sent, the rate applied and the USD banked, so every line reconciles.
Reserving holds funds without touching your balance. Confirming captures them. An expired hold returns everything automatically.
A cancellation credits your balance the same second, under the terms that applied when the booking was made, not today's terms.
A booking, end to end
POST /octo/bookings
-> 201 status: ON_HOLD
utcExpiresAt: +30 min
seats held, funds held
POST /octo/bookings/{uuid}/confirm
-> 200 status: CONFIRMED
funds captured
vouchers issued
POST /octo/bookings/{uuid}/cancel
-> 200 status: CANCELLED
refund: FULL
balance creditedQuestions
If you already speak OCTO, use the OCTO surface and you will be live fastest. If you have an existing integration written against the BeMyGuest v2 contract, point it at our v2 base URL instead; it is field-for-field compatible, so your client code does not change.
You prefund a wallet in any currency we support and we bank the USD equivalent, recording both the amount you sent and the rate used. Bookings hold funds on reservation and capture on confirmation. Refunds credit back the same second rather than in banking days.
Once there is a trading history, yes. A credit line is the same wallet with an agreed negative floor, checked when funds are held rather than when they are captured, so you cannot hold past your ceiling.
Yes, with its own credentials and bookable test inventory. Nothing in sandbox touches production, and no sandbox booking ever reaches an operator.
The hold expires on its own. Seats return to availability and held funds return to your available balance. Nothing is debited, so there is no refund to process and nothing to reconcile.
Yes, alongside the recommended selling price and, where the operator publishes one, the minimum selling price. You get all three in the same call that returns availability, which is what you need to build a search results page.
Yes. Send a reseller reference on creation and it flows through to the booking, the voucher and the statement, so reconciliation runs against your reference rather than ours.
Request access
Approved partners get sandbox credentials immediately and production keys once a test booking has been made end to end. We would rather you found the awkward parts in sandbox.