Events are signals, not the final record
Webhook deliveries may be delayed, duplicated or received out of order. A partner must not assume that the last delivered event necessarily reflects the booking’s latest state.
Check the integration path
Have an authorized developer verify the partner environment, endpoint configuration, signed request handling and response codes.
- Correct partner and sandbox/production environment?
- Reachable endpoint returning expected responses?
- Signature verification and event logging in place?
Make processing idempotent
Record event identities and avoid repeating side effects for duplicate deliveries. When ordering is unclear, retrieve the current reservation through the authorized Partner API endpoint.
Keep checkout stages separate
Hold, confirmation and payment finalization may be different steps. Missing a webhook does not by itself prove that a reservation failed; query the latest state.
Rezervem responsibilities
Partner API provides scoped technical access, Guest Network is the partner distribution model, and Manager owns the venue operation.