Calling Oracle Hospitality Distribution APIs

Environments and Base URLs

Use the following base URLs for Oracle Hospitality Distribution APIs. With Distribution API, one single endpoint for production and one single endpoint for non-production can be used to reach any property in the world (that has enabled your channel) using OPERA Cloud Distribution. Based on your location, you may decide to use one region to connect to all properties. If you are trying to minimize some potential latency, you may also decide to assign properties to one of the two regions based on property location.

Production Region URLs

Non-Production Region URLs

Note:

Confirm your internal network allow-lists, certificates, and TLS requirements for each environment before testing.

Required Headers

Include the following headers with every request:
  • Authorization: Bearer {OAuthAccessToken}
    • Obtain the OAuth access token from the Oracle Distribution Authentication API.
  • x-channelCode: {ChannelCode}
    • Channel code provided by Oracle.
  • x-app-key: {ApplicationKey}
    • A unique application key generated when you register your application in the Oracle Hospitality Developer Portal. See Viewing the Application Key.

Example Request

POST {BaseURL}/content/v1/hotels

Headers:
  • Authorization: Bearer {OAuthAccessToken}
  • x-channelCode: {ChannelCode}
  • x-app-key: {ApplicationKey}
  • Content-Type: application/json

Additional References

Parent topic: Oracle Hospitality Distribution APIs