Access control integration

Use cases

The resort managers who want to connect their access control system require the following use cases:

• Scanning the Spiagge.it reservation QR Code to access the automatic gates.

• Tracking the customers' entrance and exit.

• Validate the SIAE tickets (for the Italian aquatic park). 

• Sync of the reservations.

 NEW  (2025) Real-time integration flow 

We created a new set of APIs to simplify the integration between Spiagge.it and the third-party access control system.

We have introduced two new resource types: tickets and gates.

Each ticket is a code that a gate can scan. One ticket can be used for only one or multiple access (quantity property).

In the case of the vehicle gate, there is a property to collect the vehicle plate.

The gate resource family is used to track the ticket scanning. Tracking the ticket scanning is mandatory for aquatic parks with SIAE. 

This is the sequence scheme of the flow with the real-time validation.

 NEW  (2025) Sync integration flow 

Like the 2024 integration flow, you can use a sync logic to avoid the real-time request to the Spiagge.it API.

This integration flow has some limitations. For example, the SIAE reservation has two QR Codes, the classic Spiagge.it reservation QR Code and the SIAE QR Code. You can accept only one QR Code for each reservation using the sync integration flow.

Use case #1: Ticket sync

When someone creates or updates a reservation and his tickets data, the Spiagge.it platform notifies the action to the third-party software with the webhook.

When your application receives a webhook notification about a ticket, it has to call the ticket endpoint to get all its details.

Use case #2: Ticket scanning

When the access control system scans a ticket, it must call the tickets scan endpoint to notify the action to the Spiagge.it platform.

NB. This use case is mandatory with SIAE parks. 

Deprecated integration flow (2024)

The deprecated integration flow is based on the reservation object instead of the ticket object.

The different license settings require different implementations, so we decided to create the new integration flow.

NB. This integration flow is not compliant with SIAE requirements and features. 

Use case #1: Reservation sync

When someone creates or updates a reservation data, the Spiagge.it platform notifies the action to the third-party software with the webhook.

When your application receives a webhook notification about a reservation, it must call the reservation endpoint to get all its details.

This sync doesn't permit to have different code for each guest of the reservation.

Detect the type of the ticket (person, car, ...)

The tickets for the people and the cars are different. Two reservations are generated when customers book for one or more people and a car.

You can detect the reservation of the car by reading the spotType property. The value of the spotType property of the car reservation is "parking".

It is also possible to detect the ticket type using the services associated with the reservation.

Use case #2: Ticket scanning

This integration flow doesn't manage the ticketing scanning.