Skip to main content

Vendor Server URL Change and API Docs UI/UX Improvements

This update changes the Vendor API development (alpha) server URL and adds an important error handling guide to the Channel Create Reservation API. Readability and visual consistency across the API reference pages have also been improved.

Key Changes​

1. Vendor API Development (alpha) Server URL Change​

The server URL for the Vendor API development (alpha) environment only has changed as follows.

  • Before: https://dapi.tport.dev
  • After: https://vendor.dapi.tport.dev

Scope: all 5 Vendor API specs (Property Creation / Property Management (Sync) / Property Management (Push) / Reservation / Other API)

2. Channel Create Reservation: 400 Error Handling Guide Added​

The top of the Channel Create Reservation API page now explains how to handle the 400 channel booking number is exist already error.

This error is returned when a reservation request with the same channel_booking_number is received more than once. Do not treat it as an immediate failure (for example, by cancelling the payment). Instead, re-check the actual reservation status as follows.

  1. Call the Check Reservation API with the received channel_booking_number (use the type=channel_booking_number query parameter)
  2. If the response contains the reservation, treat it as a successful reservation and sync your internal status
  3. If there is no reservation, it is a real failure. Proceed with your usual failure handling, such as cancelling the payment

3. API Reference Page UI/UX Improvements​

The API docs have been aligned with the ONDA design system.

  • Content-type badge: an application/json badge appears to the right of the Request / Responses headings
  • Response code tab position: aligned on the same row as the description to save vertical space
  • Collapsible nested schemas: improved spacing and animation for collapsed object and array fields
  • Schema display cleanup: REQUIRED badge placement, hiding empty examples, and preserving enum values in descriptions

Contact​

If you have any questions about API integration, please feel free to contact us: