The answer
Rezervem Guest Network is the partnership and restaurant-referral network; Rezervem Partner API is the technical interface through which authorised external systems perform supported availability, booking and notification operations. They can work together, but they solve different business problems.
A hotel wants its concierge team to recommend selected city restaurants, while its developers want to show available tables inside an application. The restaurant relationship and the API connection are linked decisions, not the same contract or feature.
Guest Network answers who can refer a guest
The network concerns which categories of partners work with which restaurants and under what commercial arrangements. Restaurants may evaluate corporate programmes, hotels, concierge services, publishers and content creators.
The outcome is a managed relationship and a route for eligible referrals. The network does not give every partner unconditional access to every venue or guarantee priority seating.
Partner API answers how an application connects
Partner API supports permitted venue listings, availability queries and booking operations, including temporary holds, confirmations and supported status notifications. Payment-related checkout cases can require further steps.
The integration must account for permissions, errors and state transitions. Receiving a webhook does not necessarily replace fetching the current booking details; use the supported contract.
The two products do not replace restaurant operations
The host team continues to work in Rezervem Manager. Restaurant capacity and cancellation conditions still apply, even when a partner uses a polished customer-facing app.
Partner API also supports other approved partner types, such as POS integration scenarios, whose permissions and data differ from those of a Guest Network booking partner.
Begin with the relationship, then scope the integration
For a bank, hotel or publisher, first decide which participating restaurants and guest journey make sense. Then specify the exact read and write permissions, booking stages and data needed by the external system.
Guest Network helps frame the relationship; Partner API provides the supported technical route. Product scope and production enablement must be confirmed for the actual integration.
A practical five-point comparison
Review these points with the restaurant and relevant partners before treating any referral as a confirmed booking.
- Name the partnership goal and participating restaurants.
- Verify permissions and actual partner-venue access.
- Map availability, hold, confirmation and checkout states.
- Check the reservation's appearance in Manager.
- Agree which system tracks each operational and financial outcome.
FAQ: Can Partner API be used outside Guest Network?
Yes. Authorised POS and other integration use cases may have distinct Partner API scopes.
FAQ: Does the API decide the restaurant's commercial terms?
No. Partnership eligibility and commercial decisions remain distinct from technical operations.
FAQ: Does an API connection guarantee a booking?
No. Actual availability, confirmation and any required payment or finalisation determine the outcome.
