Connect your reservation workflow to Rezervem.
Offer restaurant availability and booking in your own platform, or connect a POS system to reservation operations. Partner API supports distinct Guest Network and POS partner workflows. Available venues, actions and guest data depend on each partner's approved access.
Every integration needs clear ownership and permissions.
A banking app needs to create bookings. A POS provider needs to match a seated guest to an existing reservation. These are different workflows, even when they share an API platform.
- 01Which restaurants can this partner access?
- 02How is availability checked?
- 03When does a booking become final?
- 04Who follows subsequent changes?
Partner API provides a defined interface for authorized partners to work with the relevant Rezervem records.
Perform actions through the API; track changes with webhooks.
Guest Network partners can list authorized venues, check availability and follow the booking flow. POS partners work with reservation and service operations according to their permissions. A webhook signals an event; use the API to retrieve the current reservation state.
Offer access to restaurants approved for your partnership.
Banking, hospitality, concierge, media and lifestyle platforms can connect to venues included in their Guest Network partnership. Venue listing, availability, booking and status tracking depend on partner category, permissions and go-live approval.
Card benefits, editorial discovery, hotel hospitality.
Banks seek a usable premium card benefit; publishers want readers to act on recommendations; hotels want the concierge journey to continue into the city. They can share a booking infrastructure without sharing the same commercial rules.
Guest data access is limited by permissions and purpose.
Authentication and fine-grained permissions govern each partner. Guest contact fields need a separate read permission, and restaurant-only notes or tags are not exposed to Guest Network partners. Access to data is not permission to use it for every purpose.
Define the use case, validate in test, then go live.
First establish whether the integration is a POS or Guest Network partnership and which venues and operations it needs. Validate authentication, booking cases, errors and webhook signatures in test. Creating reservations can require an additional go-live gate, especially for global partners.
Discuss. Build. Go live.
Start with partner type and access scope, not code.
Which ready-made integrations are available beyond Partner API?
These connections belong to the wider Rezervem ecosystem. They are not all Partner API endpoints; each integration has its own scope and status.
Common questions.
Authorized Guest Network and POS partners. The available operations differ by partner type and granted permissions.
The POS workflow concerns existing reservations and service operations. Reservation creation belongs to the Guest Network partner workflow.
No. It signals an event; retrieve the current reservation details via the authorized API.
The flow depends on payment mode. A free booking may complete at Confirm; immediate payment or authorization can require Finalize, while deferred payment follows another flow.
API references are available in test and production environments. API calls require approved partner credentials and permissions.
Guest Network is the corporate partnership and restaurant access model. Partner API is the technical interface used by approved applications.
Let's design your guest's booking journey.
Whether you're a bank, publisher, hotel or technology partner, let's map the eligible venues, your systems and the guest's last step.