Environments
Public environments
Section titled “Public environments”| Environment | Base URL | Purpose |
|---|---|---|
| Production | https://ptapi.pricetravel.com |
Live partner integrations |
| Integration | https://ptapi-int.pricetravel.com |
Pre-production testing for partners |
Partner-specific Production environments
Section titled “Partner-specific Production environments”Dedicated subdomains are assigned to specific integrations. The subdomain is provided with your credentials during onboarding; use it only if PriceTravel has assigned one to you.
| Environment | Base URL |
|---|---|
| Production (assigned) | https://ptapi-<subdomain>.pricetravel.com |
Choosing the right environment
Section titled “Choosing the right environment”| Scenario | Environment to use |
|---|---|
| Partner doing dev/QA | Integration |
| Partner doing certification | Integration → Production |
| Partner in production | Production (or partner-specific subdomain) |
Common URL pitfalls
Section titled “Common URL pitfalls”- Trailing slashes: Avoid them. The API can return 301 redirects which lose POST bodies.
- HTTP vs HTTPS: All partner-facing environments use HTTPS. Confirm with the URL provided by PT.
- Mixed environments: Do not use Integration credentials in Production or vice versa — error 1003/1004 (
invalid_client_id_for_env_<env>). - TravelGate URL: If you integrate via TravelgateX (Connect), the TravelGate service is separate from the direct API. Use the TravelGate-specific URL only for TGX-related endpoints, not for the direct booking flow.
Endpoint paths (consistent across environments)
Section titled “Endpoint paths (consistent across environments)”{base_url}/connect/token{base_url}/1.0/hotels/rates{base_url}/1.0/hotels/checkrates{base_url}/1.0/bookings/hold{base_url}/1.0/bookings{base_url}/1.0/bookings/{bookingId}{base_url}/content-catalog/hotels{base_url}/content-catalog/hotels/{hotelId}{base_url}/content-catalog/mealplans{base_url}/content-catalog/cities
