Certification Checklist
Process to certify that a partner’s integration with the Wholesalers API works correctly before production access.
Endpoints to validate
Section titled “Endpoints to validate”The certification process validates correct usage of the full booking flow:
- Token
- HotelRates
- HotelCheckRates
- BookingHold
- BookingNew
- BookingGet
- BookingDelete
Required test cases (logs to submit)
Section titled “Required test cases (logs to submit)”Test 1 — Multi-hotel search
Section titled “Test 1 — Multi-hotel search”Search for two hotels simultaneously in a single /hotels/rates call.
- Verify both hotels return rates.
- Verify each hotel’s
rateKeyis unique.
Test 2 — Single room with adult and minor
Section titled “Test 2 — Single room with adult and minor”Reservation of 1 room with 1 adult and 1 child under 17 years old.
- Pax array contains:
[{age: 30+}, {age: 0-16}]. - Verify rate correctly accounts for child age.
- Complete full booking flow through
BookingNew.
Test 3 — Three rooms, mixed configuration
Section titled “Test 3 — Three rooms, mixed configuration”Reservation of 3 rooms:
- 2 rooms with 2 adults each
- 1 room with 2 adults + 1 child under 7
- Verify multi-room rateKey returned.
- Verify amount equals sum of all 3 rooms.
- Complete
BookingHoldandBookingNew.
Test 4 — Four rooms, complex configuration
Section titled “Test 4 — Four rooms, complex configuration”Reservation of 4 rooms:
- 1 room: 1 adult + 1 child under 3
- 1 room: 2 adults + 1 child under 5
- 1 room: 1 adult only
- 1 room: 1 adult + 2 children (1 and 2 years old)
- Verify all combinations correctly priced.
- Complete full booking flow.
Test 5 — Find existing booking
Section titled “Test 5 — Find existing booking”Use BookingGet to retrieve a booking created in any prior test.
- Verify
bookingIdreturned matches. - Verify
status: CONFIRMED. - Verify that a
CONFIRMEDbooking with an emptyhotels[].confirmationCodeis handled as confirmed. - Verify that the
clientdata and hotel data returned by BookingGet match what you sent. Do not expect pax names sent in HotelRates to be returned — see BookingGet.
Test 6 — Cancel booking
Section titled “Test 6 — Cancel booking”Use BookingDelete on a booking created in prior tests.
- Wait at least 90 seconds after creation before cancelling.
- Verify response
status: CANCELLED. - Verify cancellation policies were applied correctly.
Validation criteria
Section titled “Validation criteria”PT will validate the partner’s integration against:
- Pricing accuracy: Rate increases/decreases correctly with pax configuration changes.
- Cancellation correctness: Reservations can be cancelled within the applicable policy window.
- Status handling: Partner correctly interprets CONFIRMED / CANCELLED / CREATED.
- Error handling: Partner gracefully handles 4xx and 5xx responses.
- Time window discipline: Partner respects 60min / 20min / 5min / 90s windows.
What to submit to PT
Section titled “What to submit to PT”For each test case, send logs containing:
- Full request (URL, headers excluding sensitive auth, body)
- Full response (headers and body)
eventIdfrom each response- Timestamp of each call
- Any error messages encountered
Common certification failures
Section titled “Common certification failures”| Failure | Root cause |
|---|---|
| Test 3/4 amount mismatch | Partner summing single-room rates instead of using multi-room rateKey |
| Test 6 cancellation fails | Partner cancelling within 90s cooldown |
| Unresolved booking outcome | Partner restarts the booking flow before checking BookingGet with a known numeric bookingId, or contacting PT when that ID is unavailable. |
| Certification done in wrong env | Tests run outside the Integration environment |
| Token re-requested per call | Partner not caching token, hits rate limits |
Post-certification
Section titled “Post-certification”- Production credentials issued (
client_id,client_secretfor Production env). - Partner-specific channel ID enabled in Production.
- Optional: dedicated subdomain (e.g.
ptapi-{partner}.pricetravel.com) provisioned.

