Skip to main content

Frequently Asked Questions (FAQ)

Here are frequently asked questions about ONDA API integration.

Basic Information​

Q. What is ONDA Hub?

ONDA Hub is an integrated distribution platform that connects accommodation product suppliers with sales channels.

  • Vendor (Supplier): Supply accommodation products to ONDA and sell on 70+ channels
  • Channel (Seller): Sell ONDA's 25,000+ accommodation products

Through RESTful-based APIs, you can perform real-time inventory/price inquiries, booking processing, and more.

Q. What is the difference between Vendor and Channel partners?

Vendor Partner (Supplier)

  • Hotels, resorts, pensions, and other accommodation facilities
  • PMS system providers
  • Hotel chains and product suppliers
  • Purpose: Supply accommodation products to ONDA and sell through multiple channels

Channel Partner (Seller)

  • OTA (Online Travel Agency)
  • Travel agencies and metasearch engines
  • Accommodation booking platforms
  • Purpose: Sell ONDA's accommodation products on their own platform
Q. Which partner type should I choose?

Choose according to your company's business model:

  • Do you supply accommodation products? → Use Vendor API
  • Do you sell accommodation products? → Use Channel API

For more details, please refer to the Getting Started page.

Getting Started​

Q. How long does API integration development take?

Average Development Timeline

  • Channel API: Approximately 2 weeks (average)
  • Vendor API: Approximately 1 month (1 M/M)

Actual development time may vary depending on implementation scope and development resources.

Q. How do I get an API key?

Issuance Process

  1. Sign partnership contract with ONDA
  2. Receive API key for development environment
  3. Conduct development and testing
  4. Receive API key for production environment
  5. Start official service

Contact

Q. How do I set up the test environment?

ONDA provides separate development and production environments:

Development Environment

  • URL: https://dapi.tport.dev
  • Purpose: API integration development and testing

Production Environment

  • URL: https://gds.tport.io
  • Purpose: Actual service operation

A separate API key is issued for each environment.

Technical Specifications​

Q. What are the API endpoints?

Development Environment

https://dapi.tport.dev

Production Environment

https://gds.tport.io

All APIs use the HTTPS protocol.

Q. What data format is used?

Basic Information

  • Protocol: HTTPS
  • Data format: JSON (UTF-8 encoding)
  • HTTP methods: GET, POST, PUT, PATCH, DELETE
  • Content-Type: application/json

All requests and responses are processed in JSON format.

Q. How do I authenticate with the API?

Channel API Authentication

You must include the following two keys in the HTTP header:

  1. Authorization Key

    • Header: x-api-key
    • API authentication key issued by ONDA

  2. Channel Key

    • Header: x-channel-key
    • Unique key to identify the channel

Vendor API Authentication

This follows the authentication method provided by ONDA, which will be explained in detail upon contract signing.

Integration Methods​

Q. What is the difference between Real Time Type and DB Cache Type?

Real Time Type

  • Calls ONDA API in real-time whenever a customer searches
  • No need to store inventory/rates in DB
  • No Webhook development required
  • Relatively simple implementation

DB Cache Type

  • Stores all product inventory/rates in channel DB
  • Queries own DB when customers search (fast response)
  • Webhook development required (real-time updates)
  • Advantageous for high-volume traffic handling

For more details, refer to:

Q. What is Webhook and when is it needed?

What is Webhook?

A push-based API that notifies channels in real-time when information changes in ONDA.

Webhook Types

  • contents_updated: Property/room/package content change notification
  • status_updated: Product addition or sales status change notification
  • inventory_updated: Rate/inventory change notification

When Needed

  • Required for DB Cache Type integration
  • Optional for Real Time Type

For more details, refer to Webhook Overview.

Q. What is the difference between ONDA → Vendor and Vendor → ONDA methods?

Vendor API provides two integration methods:

ONDA → Vendor (Pull method)

  • ONDA calls the Vendor system's API
  • Real-time data synchronization
  • Vendor provides API and responds

Vendor → ONDA (Push method)

  • Vendor calls ONDA API to update information
  • Sends immediately when changes occur
  • ONDA receives and stores data

In most cases, both methods are used together.

Booking and Testing​

Q. How do I use test properties?

Test Property IDs

Property IDTypeIncludes Rateplan
117417HotelIncluded
120135HotelIncluded

Important Notes

  • You cannot test with actual properties
  • Booking tests must be conducted only with the above test properties
  • You must complete cancellation processing after booking tests

For more details, refer to Test Properties for Booking.

Q. Can I query actual property content?

Yes (with conditions)

  • Prior consultation with your account manager required
  • You can query up to content information of actual properties
  • However, booking tests are strictly prohibited (use test properties only)

Please note that creating a booking with an actual property will result in a real booking.

Technical Support​

Q. Where should I send technical inquiries?

Contact Channels

Support Hours

  • Weekdays 10:00 - 18:00 (KST)
  • Emergency incidents: 24/7 response

When inquiring via email, please include the following information:

  • Partner company name
  • API type (Vendor/Channel)
  • Environment (Development/Production)
  • Specific inquiry details
Q. How should I respond to API outages?

Emergency Incident Response

Information to Include When Reporting Incidents

  • Time of occurrence
  • Error message or response code
  • Request parameters (excluding sensitive information)
  • Whether reproducible

Please provide specific information for faster resolution.

Additional Documentation​

For more detailed information, please refer to the following documents: