Getting started with Nuitee Cloud ARI

Nuitee Cloud ARI is the supplier inbound API used by PMS, channel managers, and connectivity partners to send hotel content, room/rate catalog, and daily availability and pricing to Nuitee Cloud. That data powers distribution and booking across Nuitee Cloud channels.

New here? Run the integration in your terminal first: Quick start — runnable examples (copy-paste curl, expected responses, checklist).

In simple terms

Your hotelId, roomId, and rateId are your codes — keep them identical in every API call and in webhook payloads.

Who this is for

Technical and operations teams at suppliers (PMS, channel manager, CRS, custom integrators) onboarding properties onto Nuitee Cloud.

What you will integrate

1. Static data — hotels, room/rate products, and taxes
2. ARI — date-range availability, rates, inventory, and restrictions
3. Webhooks — HTTPS endpoints on your side for live price check and reservation push

Base URLs

Authentication

Send your API key on every request:

x-api-key: YOUR_API_KEY

X-API-KEY is equivalent (headers are case-insensitive). Contact Nuitee Cloud onboarding to receive sandbox and production keys. Keys are tied to your supplier account; webhook URLs are stored on the same API key record.

Pricing models (important)

ARI pushes use pricingModel on POST /push/ari:

Use lowercase guest and unit in production payloads. Validation may accept other casing, but guest-specific fields are applied when the model is exactly guest.

Note: Older documentation referred to Daily and LOS as pricing models. The ARI gateway does not use those values. Length-of-stay rules are optional fields on each rate (minLengthStay, maxLengthStay, minStayArrival, maxStayArrival, etc.).

Recommended integration order

flowchart LR
  A[POST /push/hotels] --> B[POST /push/products]
  B --> C[POST /push/ari]
  B --> D[POST /push/taxes]
  E[Register webhooks] --> F[Go live]
  C --> F

Rules:

• Push hotels before products; push products before ARI for the same property.
• Webhook registration (steps 4–5) can happen in parallel with static setup, but your endpoints must be live before booking goes to production.
• Registering a webhook URL only stores the URL — you must implement the callback and pass end-to-end tests with Nuitee Cloud.

How the pieces connect

flowchart LR
  subgraph You["Your system"]
    PMS[PMS / channel manager]
    PC[Price-check URL]
    PB[Push-booking URL]
  end

  subgraph NC["Nuitee Cloud"]
    ARIgw[ARI gateway]
    Core[ARI core engine]
    Book[Booking API]
    Worker[Reservation delivery]
  end

  PMS -->|POST /push/hotels, /products, /ari| ARIgw
  ARIgw --> Core
  PMS -->|POST register webhooks| ARIgw
  Book -->|POST live price check| PC
  Worker -->|POST reservations| PB

Supplier codes (hotelId, roomId, rateId) in your API calls are mapped to Nuitee Cloud internal IDs. Use the same codes in static data, ARI, and when interpreting webhook payloads.

Obtaining API credentials

1. Nuitee Cloud account — contact support or onboarding for supplier access.
2. API key — request sandbox and production keys for the ARI environment.
3. Authentication — send the key in the x-api-key header on all requests.

Key APIs for integration

Optional platform endpoints (confirm with onboarding): POST /push/getHotels, POST /push/getRoomRateMappings, POST /push/getTaxes, POST /push/webhook/booking, GET /push/webhook/pushbook/retrieve.

Next steps

• Static data — Hotels content
• ARI push — Availability - Rate - Inventory
• Booking — Retrieve/Push bookings
• Webhooks — Receive notifications for the following actions: booking, cancellation, and price check.