Search live hotel availability and book with idempotent confirms. Then let Trekko's engine quietly rebook your customer at a cheaper rate after they've booked — and credit the savings back to you. Get test keys with a verified company email, no call required.
trk_test_ key + secret are issued automatically. Under a minute. No sales call, no manual review.trk_live_ key, adding the payment step.# 1) self-serve signup (any non-disposable email) → 202, we email you a 6-digit code curl -sS -X POST https://api.trekko.co/core/sandbox/signup \ -H "Content-Type: application/json" \ -d '{"email":"dev@acme.com","company_name":"Acme"}' # 2) confirm the code → 201 with your test key (secret shown once). Didn't get it? POST .../signup/resend curl -sS -X POST https://api.trekko.co/core/sandbox/signup/verify \ -H "Content-Type: application/json" \ -d '{"sandbox_account_id":123,"code":"123456"}' # 3) first call (sandbox base URL + test key) B=https://api.trekko.co/core/sandbox curl -sS -X POST "$B/accommodation/search?query=Barcelona" \ -H "Authorization: ApiKey trk_test_xxx:secret" \ -H "Accept-Language: en"
Instant — issued automatically the moment you confirm the 6-digit code we email to your company address (no free or disposable mailboxes, no human review). Hits the isolated sandbox — deterministic catalog, no real vendors,
money or production data. Build and verify your entire integration here, including the
booking.rebooked flow via the rebooking simulator.
Real availability and bookings, attributed to your agency in Trekko's CRM with your markup. Issued after Trekko approves your production access request and your wallet deposit reaches the minimum (€3,000). Same paths as test with a payment step added between checkout and confirm; see the sandbox differences.
Search → availability (markup-inclusive) → checkout → confirm → cancel → list. Idempotent confirms; stable error codes.
Car rentalSearch → book → cancel with the cancellation and no-show terms structured on your price (no_show_fee, capped_at_total).
Airport and city transfers or a chauffeur by the hour: search, paid add-ons, book, cancel and an agency-branded PDF voucher.
RebookingTrekko rebooks confirmed, refundable stays at cheaper rates and credits the savings to your wallet or credit balance. A stable booking_id survives the change.
booking.rebooked and booking.hotel_confirmed delivered with an HMAC Trekko-Signature, retried up to 3 times within seconds, deduped by event_id.
A trigger_rebooking endpoint runs the exact money model on demand, so you can test savings + webhooks without waiting.
Live paths are under /core; the sandbox (/core/sandbox) mirrors most of them, with the differences noted below. Full schemas in the reference.
| Area | Method & path |
|---|---|
| Signup (sandbox) | POST /sandbox/signup → POST /sandbox/signup/verify (resend: POST /sandbox/signup/resend) |
| Search | GET /accommodation/search?query=… (sandbox: POST) |
| Availability | POST /accommodations/get_accommodation_availability |
| Destination search (live) | POST /accommodations/list_available_accommodations (streamed) |
| Checkout → Pay → Confirm | POST /accommodation/bookings/{checkout,pay_by_funds,confirm_booking} (sandbox: no pay step) |
| Cancel · Get | POST /accommodation/bookings/{cancel_booking,get_booking} |
| List | GET /accommodation/bookings/list_bookings?page_no=… (sandbox: POST) |
| Account | POST /accommodation/account/{balance,savings} |
| Webhooks | POST·GET·DELETE /accommodation/webhooks |
| Car rental (live) | GET /extras/cars/locations?q=… · POST /extras/cars/{search,book,cancel} |
| Transfers & hourly (live) | POST /extras/transfers/{search,pricing,book,cancel} · GET /extras/transfers/{bookings,voucher} |
| Rebooking simulator (sandbox) | POST /accommodation/bookings/trigger_rebooking |
REST only; SDKs are planned.
No client library is published or supported yet: there is no Trekko package on npm or PyPI,
so do not add one to your manifest. Integrate over HTTPS with curl, Postman or your own HTTP
client, or generate a typed client from the OpenAPI spec on this page with
openapi-generator.
Register an HTTPS endpoint and Trekko POSTs signed events.
Verify Trekko-Signature: t=<unix>,v1=<hex> where
v1 = HMAC_SHA256(secret, "<t>.<raw_body>") over the raw body; reject if it doesn't match
or |now − t| is more than five minutes. Dedupe on event_id (at-least-once).
Emitted today: booking.rebooked and booking.hotel_confirmed
(booking.confirmed and booking.cancelled are not emitted yet). Answer 2xx within
10 seconds and do not redirect: failures are retried 3 times within seconds, so reconcile with
get_booking. Examples in the integration guide.
{
"event": "booking.rebooked",
"event_id": "evt_9f2c…",
"created_at": "2026-06-20T14:03:11Z",
"data": {
"booking_id": "TK-1045",
"partner_savings": 50.00,
"credited_to": "virtual_wallet"
}
}
Integrate against the sandbox with your trk_test_ key until the full loop + webhook verification pass.
Top up your Trekko wallet (card or bank transfer) with a deposit of at least €3,000 — the funds you spend on real bookings. Bank transfers are confirmed by Trekko.
Request production access (company email check and Trekko review). Once it is approved and your balance reaches the minimum, your trk_live_ key is issued, attributed to your agency with your markup.
Swap the base URL to /core and the key to trk_live_, add the payment step and handle the production-only errors (402, 409, 429).
Heads-up: live search and bookings need a funded wallet. Calls made before the €3,000 minimum deposit clears return a clear error telling you to top up.
Open the console — get a key & go live →
Reference: OpenAPI reference · Going to production · Integration guide · Rebooking & savings · Sandbox · Postman collection
The contract version is the date in the OpenAPI info.version. Changes are additive where
possible (new optional fields, endpoints and error codes), so ignore unknown fields and unknown error.code
values; Trekko does not make breaking changes without notice to registered integrators. For support use the
Trekko Developer Support contact published with the API reference and quote the X-Request-Id of the failing call.
A key can do everything your agency can, so keep it server-side and restrict outbound access from your own network.