Agency β setup & selling
The agency is set up once; after that it's not repeated clicking, it's an API integration. The panel offers little self-service (keys + live request) β the real work is API calls from the agency's own system.
Partnership application
The agency opens partner.travapi.com and applies with company, tax and contact details; the application reaches our team.
Create your own password after approval
Once approved, the agency receives an email and sets its own password from the link. (The approval step is on the admin side β below.)
Sign in, reach the API Access panel
The agency signs in with email + password and reaches the API Access panel. In the panel its only job is managing keys.
Create a sandbox key
The agency creates a sandbox (test) key with one click. The secret is shown only once; the key appears in the list.
Request live selling
For live selling the agency opens a request via "Request live access"; Woxx approves it and the live key activates.
From its own system: token β search β sell
The agency's day-to-day is not in the panel but in its own software: it gets a token with the key,
searches hotels/tours/cruises, and books with the chosen rateKey. No real charge in sandbox.
SBX- sandbox booking (no charge).Admin (Woxx) β commercial settings
The agency's money is configured here: markup at approval, quota/IP/scope in key management, credit in the current-account limit. The Woxx admin owns all commercial terms.
Sign in to the management panel
The Woxx admin signs in to the management panel, from where applications, agencies, keys and reservations are handled.
Approve the application, assign the commission margin
The admin sees pending applications under "Acente BaΕvurularΔ±" (Agency Applications). On approval the admin enters a markup % β the agency + user are created and a set-password email is sent.
The agency record
The approved agency appears in the "Acenteler" (Agencies) list β company, tax office, contact and reservation count. Commercial settings such as markup, source market and cruise commission are edited from the agency detail.
API keys: issue, restrict, monitor
The admin issues keys for the agency and defines scope (hotel/tour/cruise), allowed IPs, daily quota and rate limit. Usage analytics (call count, error rate, latency, endpoint breakdown) are monitored live. Keys can be suspended / revoked; a live key activates after approval.
Operator (TRMS) β reservation & account
Every live booking the agency makes via the API lands in TRMS. The operator sees it attributed to the agency, tracks its financials (sale/net/commission) and manages the agency's current account.
The operator sees all reservations
The TRMS reservation list combines source (Travapi / WOXX B2B / Reswioβ¦), supplier, hotel/product, sale amount and status. The Agency filter narrows to a single agency's reservations.
Agency-attributed detail with financials
The detail shows which agency the reservation belongs to (Kaya Travel Agency), the supplier (Woxx), dates, the sale / net / commission breakdown and payment status. From here the operator handles confirm/cancel/refund, voucher and invoicing.
Current account: credit limit & balance
In card-free (account) selling, each booking posts a debt to the agency's current account. The operator monitors/manages the agency's credit limit, available balance and transactions from here.
