Webhooks overview
You host HTTPS endpoints on your infrastructure. Nuitee Cloud calls them during booking (price check) and when delivering reservations (push booking).
Register URLs with curl: Quick start — Step 4
Registering webhooks
Both registration endpoints accept:
{ "webhook": "https://your-domain.example/hp/callback" }| Webhook | Register via | Stored as |
|---|---|---|
| Price check | POST /push/webhook/availability | Availability / price-check URL on your API key |
| Push booking | POST /push/webhook/pushbook | Push-booking URL on your API key |
Registering a URL only saves it on your API key. Implement and test the endpoint before go-live.
Which webhooks do I need?
flowchart TD Q[Live price validation at book time?] Q -->|Yes| A[Register POST /push/webhook/availability] Q -->|No| B[Confirm with onboarding] R[How do you receive reservations?] R -->|HTTP push| C[Register POST /push/webhook/pushbook] R -->|Pull API| D[GET /push/webhook/pushbook/retrieve if enabled]
Comparison
| Aspect | Price check | Push booking |
|---|---|---|
| Registration | POST /push/webhook/availability | POST /push/webhook/pushbook |
| When HP calls you | During book flow (live validation) | On reservation create/cancel + scheduled job |
| You return | Live price / availability | ACK / process reservation |
| Details | Price check | Push booking |
Authentication
Send x-api-key when registering webhooks. For inbound calls from Nuitee Cloud to your URLs, confirm with onboarding whether Nuitee Cloud sends a signature, API key, or other auth.