Skip to main content

Technical Validation Criteria

Before Travelgate starts developing your connector, every Seller API goes through a technical validation. This page explains what we check, why it matters, and what you need to send us — so the development phase starts faster and the resulting connection delivers high-quality product to our Buyers.

Two levels of requirements
  • Mandatory — your API must meet these criteria for development to begin.
  • Highly recommended — not blockers, but essential for your product to be competitive in the Marketplace.

What your API must provide (mandatory)​

These checkpoints are non-negotiable. If any of them is missing, the integration cannot move forward.

1. Complete documentation and working authentication​

We need detailed endpoint documentation and a comprehensive list of error codes, plus a stable authentication flow (OAuth, API Key, etc.) that is fully functional in your test environment. Without this, our team cannot reliably build or troubleshoot the connector.

2. A standard booking flow​

Your API must support the standard shopping flow:

Search → Quote (if applicable) → Book

It must also focus on standard accommodation with daily check-in. We do not currently integrate packages, last-minute hourly offers, or non-standard booking units through this flow.

3. Structured cancellation policies​

Cancellation policies protect both the Buyer and the Seller, so we cannot work with free-text descriptions. Every policy must include:

  • Start date and end date
  • Penalty amount and penalty type (Amount, Percentage, or Number of Nights)

The policy logic must allow a direct or algorithmic mapping to the Travelgate model.

4. Compatible payment types​

Your API must support at least one of these payment types:

MERCHANT · DIRECT · CARD_BOOKING · CARD_CHECK_IN

Your integration might technically work without these, but they make a real difference in how your product performs on the Buyer side.

RequirementWhy it matters
Request/Response examplesDramatically reduces development time and troubleshooting.
Defined meal plansIf not provided, Travelgate assumes "Room Only", lowering your product's value.
Category codes and descriptionsWithout them, your hotels are listed as "NC" (No Category), reducing competitiveness.
Meal plan listEssential for mapping and filtering on the Buyer side.
Geocoding and address dataRequired for accurate hotel mapping (latitude/longitude, name, country).
Real-time cancellation statusNeeded to confirm the success of a cancellation request.

Technical checklist before development​

Make sure your API supports these capabilities before the Development phase begins.

Performance & scalability

  • Stable response times under load. Scalability testing is mandatory to ensure your production environment can handle Travelgate's traffic volumes.

Availability & inventory

  • Multi-hotel search — search by a list of hotel codes in a single request.
  • Unique identifiers — every option/room returned must have a unique identifier to prevent booking errors.

Static data (content)

  • Hotel list endpoint (mandatory) — retrieve your full portfolio of hotel codes.
  • Destination tree (recommended) — your destination structure for better geographic filtering.

How to submit your API for validation​

Once your API meets the mandatory and high-priority criteria, send us the following:

  1. Requirements template — download the Seller API Technical Requirements Template and return it with columns G and H fully completed.
  2. Production-like sandbox access — credentials for a testing environment.
  3. API request examples — a collection of example requests and responses covering a full Search-to-Book flow.
  4. Mapping tables — specifically for Room Types, Meal Plans, and Cancellation Penalties.
tip

The more complete your submission is (documentation, examples, and mapping tables), the faster our team can validate your API and start the connector development.

Annex: criteria reference codes​

The requirements template uses internal reference codes for each criterion. Use this table to map the criteria above to the codes in the Excel file.

CodeCategoryCriterion
DOC-01, DOC-02, DOC-04DocumentationFull endpoint documentation and error code list
DOC-03DocumentationRequest/Response examples
AUTH-01, AUTH-02SecurityStable authentication flow in test environment
FUN-02Booking flowStandard Search → Quote → Book flow
AVAI-01AvailabilityMulti-hotel search in a single request
AVAI-06AvailabilityUnique identifier per option/room
AVAI-07AvailabilityStandard accommodation with daily check-in
AVAIL-05AvailabilityDefined meal plans
CAT-01CategoriesCategory codes and descriptions
MEAL-01Meal plansMeal plan list
HINFO-01Hotel infoGeocoding and address data
CNP-01CancellationStructured policy data (dates, amount, type)
CNP-04CancellationMappable policy logic (no free text)
CNX-01CancellationReal-time cancellation status
PAY-01PaymentAt least one supported payment type
PER-01, PER-02PerformanceStable response times and scalability testing
HLIS-01ContentHotel list endpoint
DES-01ContentDestination tree