> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anny.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Arivo with anny

> The barrier of your Arivo garage opens for the license plate of a confirmed booking.

[Arivo](https://garage.arivo.app/) runs parking garages with license plate recognition. With this integration, anny creates a pre-booking in your garage for a confirmed booking. The barrier opens when the plate is recognized during the booked time.

With Arivo you can, in anny:

* Send the license plate of a booking to the garage as a pre-booking
* Extend access by a buffer before and after the booking
* Open several entrances by selecting several templates in one rule
* Forward time changes, plate changes and cancellations to Arivo

The integration fits visitor parking, company garages and car parks where the barrier should open without a ticket or a key.

> [!NOTE]
>
> Available from the Professional plan.

## Typical use cases

| Use case | Description |
| - | - |
| Visitor parking | **Barrier only inside the booked window.** Guests enter the license plate when they book. Arivo opens the barrier as soon as it recognizes the plate. |
| An area with individual bays | **One rule for the whole area.** A rule on the parent resource also covers bookings of the bays underneath. |
| A garage with several entrances | **Every barrier from one booking.** You select several pre-booking templates. anny creates one pre-booking per template. |

## How the Arivo connection works

You enter the credentials of a service account that Arivo created for you. anny checks the **Client ID** and **Client secret** with Arivo before saving them. After that, anny renews the access on its own. If Arivo rejects the credentials, nothing is saved.

You do not pick the garage from a list. Arivo offers no way to look up garages. You copy the **Resource ID** from the Arivo Parking OS. The Pre-Booking app has to be installed for that garage. anny can load the pre-booking templates only after you have saved the **Resource ID**.

For every confirmed booking that has a license plate, anny creates one pre-booking per selected template. The window is the booking time plus **Access before booking** and **Access after booking**. The times are sent in your organization's time zone. The garage has to sit in that same time zone.

anny reshapes the plate for Arivo. "K AN 2020" becomes "K:AN2020". Spaces, hyphens and dots are removed. A colon sits between the area code and the rest.

The booking confirmation says: "Your selected license plate will open the gate upon arrival." On the booking, the access sits under **Connected data** in **Smartlock accesses**. It shows **Your license plate will be scanned**. As **Door lock**, anny shows "Arivo-" followed by the reshaped plate.

If you change the time or the plate, anny updates the pre-booking. Once the booking has started, anny changes only the end. A window that has already ended can no longer be moved in Arivo. If you remove the plate, anny cancels the pre-booking. The same happens when the booking is cancelled, declined or deleted.

For a series booking the access starts as **Scheduled**. anny creates the pre-booking about 48 hours before it begins.

anny does not learn when a vehicle enters or leaves. Arivo decides the barrier from the pre-booking.

| Data | Direction | Frequency |
| - | - | - |
| License plate and time window of the booking | anny → Arivo | On a confirmed booking, and again when the time or the plate changes |
| Cancellation of the pre-booking | anny → Arivo | When the booking is cancelled, declined or deleted, or the plate is removed |
| Pre-booking templates of the garage | Arivo → anny | After the resource ID is saved, when you open the rule |

## Connect Arivo

### Requirements

Before you connect Arivo, make sure that:

* your Arivo account is set up and the Pre-Booking app is installed for the garage,
* you have the **Client ID** and **Client secret** of the service account from Arivo,
* you can copy the garage **Resource ID** from the Arivo Parking OS,
* the parking area exists as a resource in anny,
* every service of that resource asks for the license plate with a required field of type **License plate**.

### Set up the connection

**1. Check the credentials**

In the sidebar, open **Account** → **Apps & Integrations**. Under **All Apps and Integrations**, choose the **Arivo** tile and click **Set up**. Enter the **Client ID** and **Client secret**, then click **Verify authentication**. anny saves the credentials only when Arivo accepts them.

A second garage is a separate connection via **Add another**. Each connection has one **Resource ID**.

**2. Enter the garage**

In the **Garage** section, enter the **Resource ID** from the Arivo Parking OS and click **Save**. Until you save, the templates stay empty.

**3. Create a rule**

Open **Access through bookings** and click **Add**.

1. Under **Select resource**, choose the parking area.
2. Under **Pre-booking templates**, choose one or more templates. If Arivo does not return a list, you can type the template ID.
3. Under **Custom field for license plate**, choose the license plate field.
4. Set **Access before booking** and **Access after booking**.
5. Click **Confirm**, then **Save**.

**4. Activate the connection**

Switch the toggle at the top right to **Integration active**. Then create a test booking with a license plate and check the pre-booking in the Arivo Parking OS.

Once the connection is active and a rule matches, anny creates the pre-booking in Arivo for new confirmed bookings.

> [!TIP]
>
> A resource can have only one rule. Several entrances belong in the same rule, as several **Pre-booking templates**. A rule on the area also covers the bays underneath. If a bay has its own rule, that rule applies.

### Settings and options

| Setting | Description |
| - | - |
| Client ID | Identifier of the service account Arivo created for you. |
| Client secret | Secret for that client ID. anny checks both values before saving them. |
| Resource ID | The garage in the Arivo Parking OS. anny cannot list garages, so you paste the ID. |
| Pre-booking templates | Templates of that garage. One pre-booking is created per template. |
| Resource | Parking area whose confirmed bookings trigger a pre-booking. |
| Custom field for license plate | Field of type **License plate** that anny reads the plate from. |
| Access before booking | Time before the booking starts, during which the barrier already opens. |
| Access after booking | Time after the booking ends, during which the barrier still opens. |

You enter new credentials while the integration is not active. If it is active, deactivate it first. Otherwise anny rejects the change.

## Limitations

The Arivo integration does not support:

* Access for community members. Memberships have no license plate, so anny does not create a pre-booking for them.
* Remote opening. The barrier opens only when Arivo recognizes the license plate.
* Check-in or check-out when the plate is recognized. anny does not hear about the passage.
* A list of garages. You copy the **Resource ID** from the Arivo Parking OS.
* Several garages in one connection. For another garage, use **Add another**.
* Bookings that are not confirmed, bookings without a customer, or internal blockers.
* A license plate field that is not a required field of type **License plate**, or that is missing on a service of the resource.

## Disconnect

> [!WARNING]
>
> If you deactivate the integration, existing pre-bookings in Arivo stay valid until the end of their time window. New bookings no longer receive access. Deleting removes the accesses stored in anny. The pre-bookings in Arivo are not cancelled by that and expire on their own.

You find both under **Integrations**: deactivate with the **toggle** at the top right, delete via the **three dots** → **Delete**.

## FAQ

> **When does the barrier open?**
>
> As soon as Arivo recognizes the license plate of the confirmed booking inside the valid window. The window is the booking time plus **Access before booking** and **Access after booking**.

> **Can one booking open several entrances?**
>
> Yes. Select several **Pre-booking templates** in the rule. anny creates one pre-booking per template, with the same plate and the same window.

> **Does the access also cover community members?**
>
> No. Arivo depends on the license plate of a booking. A membership on its own does not open the barrier.

> **What happens with a series booking?**
>
> The access starts as **Scheduled**. anny creates the pre-booking about 48 hours before the individual appointment, not when you create the series.

> **Which field has to ask for the license plate?**
>
> A required field of type **License plate**, on every service of the resource. anny reads only the field you select under **Custom field for license plate**.

## Troubleshooting

> **The barrier does not open even though there is a booking**
>
> Check that the booking is confirmed and that a license plate is stored in the mapped field. Check the window under **Smartlock accesses**, including the buffer. If the garage looks offline, try again later. If Arivo rejects the window, check the template's duration limits and the garage's booking contingent in the Arivo Parking OS.

> **Pre-booking templates shows no options**
>
> Save the **Resource ID** in the **Garage** section first, then open the rule again. If Arivo still does not return the list, type the template ID. Also check that the Pre-Booking app is installed for the garage and that the service account may use it.

> **The rule or the garage cannot be saved**
>
> Every service of the resource needs the selected license plate field, and the field has to be required. Every rule needs at least one template, and the **Resource ID** has to be set. You can use the same resource only once.

> Important information for agents:
>
> **UI path:** Sidebar **Account** → **Apps & Integrations** (`/apps`) → **All Apps and Integrations** → **Arivo** tile → **Set up**. Existing: **Your apps** → **Arivo**. Credentials: **Client ID**, **Client secret**, button **Verify authentication**. Section **Garage**: **Resource ID**, then **Save**. Rules: **Access through bookings** → **Add**. Fields: **Select resource**, **Pre-booking templates**, **Custom field for license plate**, **Access before booking**, **Access after booking**, **Confirm**. Toggle in the page header: **Integration active** / **Integration inactive**. Three-dot menu: **Delete**, **Remove authentication**, **Test connection**, **Rename**. Second garage: **Add another**. Booking: **Connected data** → **Smartlock accesses**. Detail fields: **Status**, **Access begins at**, **Access ends at**, **Door lock**, **Created at**, **Error**. Hint on the access: **Your license plate will be scanned**.
>
> **Authentication:** Service-account client credentials, no OAuth redirect. Checked before save. Rejected credentials are discarded. New credentials only while the integration is not active, otherwise "Please deactivate the integration before doing this action." anny renews the access afterwards.
>
> **Triggers:** Confirmed bookings with a customer only. Blockers get nothing. Blocker becomes a booking: access is created. Booking becomes a blocker: the pre-booking is deleted. Status leaving confirmed: delete. Time change: update, and once the booking has started only the end. Expired window: no further change. Resource change: recreate. Plate removed: delete the pre-booking, status failed. Series: status **Scheduled**, created about 48 hours before the start. A rule on the parent resource covers child bookings. A rule on the bay itself wins. One rule per resource.
>
> **License plate:** Required field of type **License plate** on every service of the resource. anny reshapes it: area code, colon, the rest without separators, uppercase. "K AN 2020" becomes "K:AN2020". The access name is "Arivo-" plus that plate. Mail text: "Your selected license plate will open the gate upon arrival."
>
> **Quirks:** One garage per connection (**Add another** for the next). Templates load only after the **Resource ID** is saved, not from an unsaved draft. If the list fails, template IDs can be typed. The organization time zone is treated as the garage time zone. anny does not clean up expired pre-bookings. They expire in Arivo. Deactivating stops new pre-bookings. Existing ones remain. Deleting the integration removes the accesses in anny and does not cancel the pre-bookings in Arivo. Cancelling a single booking does cancel its pre-booking. No community access, no remote open, no scan check-in. Admins get an email when Arivo rejects the booking, does not know the garage or template, the garage is offline, or the credentials are rejected.
>
> **Not this:** Not Comydo. Comydo confirms scans by webhook and can check in and out on a scan. Arivo receives a pre-booking and opens the barrier itself.
>
> **Relationships:** Smart lock integrations feature, from Professional. Related articles: [Smart lock integrations](/en/smart-locks-overview), [Comydo](/en/comydo), [Parking](/en/getting-started-parking).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.