API out

Turn your travel platform into a distribution business.

Open new B2B revenue channels by distributing selected flight and hotel inventory to agencies and platforms — while controlling each partner's content, pricing, credit, and permissions.

Plan my distribution setup→See how it works

What distribution gives you

Add distribution partners without rebuilding the operation for each one.

Your partners integrate once with Tripklik. You decide what they can sell, what prices they receive, and how they can book. Tripklik manages the connected supplier workflows behind the API.

Reach more sellers without connecting every partner to every supplier.

Distribute selected flight and hotel content from your connected suppliers and direct contracts through one consistent API. Partners receive one integration while you expand the reach of your inventory.

  • One integration for every partner
  • Flights and hotels from the same structure
  • You choose what each partner can see

Grow distribution reach without maintaining separate supplier connections for every partner.

Content availability follows the relevant supplier agreement and the configuration you enable — not every supplier permits redistribution.

See capabilities

Flight sources you can distribute

Give partners access to selected content from:

  • GDS connections
  • NDC suppliers
  • Direct airline APIs
  • Low-cost carriers
  • Flight aggregators
  • Private and negotiated fares

Hotel sources you can distribute

Partners can receive selected content from:

  • Global bedbanks
  • Online hotel suppliers
  • Regional suppliers
  • Direct hotel contracts
  • Tripklik hotel extranet inventory

Your sources7

TripklikOne APIDistributing

Your partners6

Switch a source or a partner off to see what each side receives.

One API. Different content, prices, and permissions for every partner.

Control what each API client can search, sell, and manage. Tripklik automatically applies the correct supplier access, pricing agreement, currency, market rules, and booking permissions.

  • Separate credentials and rules per partner
  • Pricing, currency and market rules applied automatically
  • Booking actions enabled per partner

Protect commercial agreements while serving different partner models.

See capabilities

Set per API client

Create separate API credentials and business rules for every connected partner.

  • Available products
  • Flight and hotel suppliers
  • Airlines and destinations
  • Private fare access
  • Markups and markdowns
  • Currency and exchange rates
  • Wallet and credit limits
  • Search limits
  • Booking permissions
  • Hold, cancel, confirm, issue, and void permissions

One partner may receive hotel inventory only, while another receives flights and hotels with a different pricing agreement.

Configuration

Products
Flights · Hotels
Suppliers
Amadeus · LCC · Hotelbeds
Private fares
Enabled
Markup
5%
Currency
SAR
Funding
Wallet + credit
Search limit
12 per second

What this partner gets

InventoryFlights and hotels, private fares included
Partner priceSAR 1,050
Your marginSAR 50
Booking actionsHold · Confirm · Issue · Cancel
Financial requirementBalance checked before each chargeable action

Same platform, same suppliers — two completely different commercial agreements.

Every chargeable action stays inside the financial limits you set.

Give partners a prepaid wallet, an approved credit facility, or both. Tripklik checks available funds before eligible chargeable actions and records deposits, bookings, cancellations, refunds, and adjustments in the financial ledger.

  • Wallet, approved credit, or both
  • Funds checked before chargeable actions
  • Every movement written to the ledger

Increase partner volume while controlling financial exposure.

Refunds and balance adjustments follow the airline, hotel, supplier, payment provider, and contractual process — they are not always immediate.

See capabilities

How partner funding works

API bookings can be connected to the same wallet and credit management system used by the Tripklik B2B portal.

  • A prepaid wallet
  • An approved credit limit
  • A combination of wallet and credit

Every deposit, booking, cancellation, void, refund, and adjustment is added to the partner's financial ledger.

Financial ledger · Sky TravelReconciled ✓
WalletSAR 12,500
Credit availableSAR 15,000
Total availableSAR 27,500
DateDescriptionAmount
12 SepTicket K7L2XQ− SAR 780
12 SepDeposit+ SAR 10,000
11 SepRefund HT-58213+ SAR 1,100

Every movement recorded — date, value, booking, user. Try the buttons.

Protect every request from duplicate bookings to final status.

Tripklik applies authentication, permissions, request controls, transaction history, and booking safeguards across the partner network. Your team can see what happened, who initiated it, and how the supplier responded.

  • A repeated request never books twice
  • Price and funds re-checked before booking
  • Full history of what the supplier returned

Reduce booking errors, improve traceability, and protect supplier performance.

See capabilities

Access controls

API access uses secure credentials assigned to each partner.

  • Separate sandbox and production credentials
  • Token-based authentication
  • IP address restrictions
  • Request signatures
  • Role-based permissions
  • Rate limits
  • Idempotency keys
  • Complete request and response logs
  • Sensitive data masking

Traffic controls that protect suppliers

Tripklik monitors how every partner uses the API.

  • Requests per second
  • Daily search limits
  • Look-to-book ratio
  • Concurrent requests
  • Search timeout
  • Duplicate search detection
  • Supplier-specific traffic rules
  • Temporary access suspension

These controls help protect supplier agreements, response speed, and infrastructure stability.

Status updates partners receive

Webhooks tell the partner system when something changes:

  • Flight booking held
  • Ticket issued
  • Booking cancelled
  • Ticket voided
  • Hotel booking confirmed
  • Hotel booking cancelled
  • Price changed
  • Payment completed
  • Refund completed
  • Wallet balance changed

Webhook requests can be signed so the receiving system can verify that the notification came from Tripklik.

  1. Partner identifiedCredentials and permissions checked
  2. Search acceptedWithin the partner’s traffic limits
  3. Offer returnedNormalised across the permitted suppliers
  4. Price re-checkedRevalidated with the supplier
  5. Duplicate checkIdempotency key compared
  6. Funds checkedWallet and credit verified
  7. Sent to supplierBooking request issued
  8. Supplier response recordedWritten to the transaction history
  9. Partner confirmedResponse returned to the partner
  10. Status update sentWebhook to the partner system

Booked · partner and your team both see the same status

One integration

One partner integration for flights and hotels

Partners work with one consistent Tripklik structure while the platform manages the different supplier communications and booking rules behind it.

Search → Compare → Revalidate → Hold or book → Issue when eligible → Retrieve documents

  • Multiple flight sources
  • Consistent result structure
  • Fare, baggage, and rule information
  • Controlled post-booking actions
View supported operations

Supported flight operations

  • Airport and city search
  • One-way searches
  • Round-trip searches
  • Multi-city searches
  • Fare details
  • Baggage allowance
  • Fare rules
  • Price revalidation
  • Booking creation
  • PNR retrieval
  • Hold booking
  • Ticket issuance
  • Booking cancellation
  • Ticket void
  • Refund requests

Available operations depend on the enabled supplier and the conditions of the selected booking.

How the integration runs

One request path, from search to confirmed status

A partner integrates once against this flow. The endpoint reference, error codes, webhook payloads and full operation lists live in the developer documentation.

What partners receive to integrate

Partners receive the resources needed to complete the integration:

  • API documentation
  • Endpoint descriptions
  • Request and response examples
  • Error-code reference
  • Postman collection
  • Sandbox credentials
  • Test scenarios
  • Certification process
  • Production credentials
  • Technical support

The exact endpoints, fields, and supported operations are defined in the current Tripklik API documentation and may differ by supplier capability.

From partner setup to live distribution

You are not left to integrate and support every partner alone.

Tripklik works with your team to configure the distribution model, prepare integration resources, test booking and financial workflows, support certification, and investigate operational issues after launch.

  1. Design

    Define products, suppliers, markets, commercial rules, credit models, permissions, and expected partner traffic.

  2. Integrate

    Provide the agreed documentation, examples, sandbox access, test scenarios, and technical guidance.

  3. Certify and launch

    Validate search, booking, payment, error-handling, webhook, and operational workflows before production access is enabled.

  4. Operate and grow

    Support issue investigation, supplier and technical escalation, traffic monitoring, new partner configurations, and future distribution requirements.

Meet the team behind your API launch→

Design your travel distribution network with Tripklik.

In a working session, we will review the content you can distribute, the partners you want to serve, your pricing and credit model, and the integration support required to launch.

Plan my distribution setup→Request sandbox access