Skip to main content
Custom Remote Open is the open variant of remote opening: instead of connecting a specific locking system, you store your own endpoint URL. When an authorized person presses the open button in anny, anny sends a request to that URL. What happens next is decided by your own system. With Custom Remote Open, you can do the following in anny:
  • connect a locking system for which there is no ready-made integration
  • give customers an open button for their booking time
  • give community members permanent access to selected devices
The integration is especially handy when you already open doors, gates or barriers through your own control system and only want to connect that control system to your bookings.
Available from the Professional plan.

​
Typical use cases

​
How the Custom Remote Open connection works

The connection consists of two pieces of information: the endpoint URL of your system and an endpoint token that anny generates for you. anny sends the token with every request as Authorization: Bearer <token>. Your endpoint checks the token and triggers the opening. anny does not query your system at any other time. There is no device list that anny retrieves, and no status query at the lock. The only contact is the opening request at the push of a button. Access rights are created exclusively in anny. Here is how an access works:
  1. A booking is accepted. anny checks whether a rule covers the booked resource.
  2. anny creates an access right with the status Successful for each device ID in the rule. Your system does not receive a request at this point.
  3. During the valid period, customers see the open button in anny.
  4. On click, anny sends the request to your endpoint URL and evaluates the response.
The request is a POST with the following details: anny shows the matching example request directly in the integration settings under Example request. Only the response status of your endpoint counts for success. If it responds successfully, anny reports the opening as successful. If it responds with an error or is unreachable, customers see Opening failed. If you regenerate the token, the old token immediately loses its validity and all requests fail until your endpoint knows the new token.

​
Connect Custom Remote Open

​
Requirements

Before you connect Custom Remote Open, make sure you have the following:
  • Admin rights in your anny account and the Professional plan
  • a publicly reachable endpoint in your system that accepts POST requests with JSON and starts with https://
  • a check of the bearer token in your endpoint, so no one can open without authorization
  • logic that opens the correct device based on the passed device ID
  • defined device IDs, because customers see this ID as the name of the door lock

​
Set up the connection

1

Store the endpoint

Open the Integrations from the menu bar and go to Custom Remote Open. Under Settings, enter the endpoint URL and save. Then click Generate token and copy the endpoint token immediately, because anny shows it only once. Then store the token in your own system.
2

Configure

As soon as the endpoint URL and token are saved, the sections for rules appear. Create your access rules there:
  1. Under Access through bookings or Access through communities, click Add.
  2. Select the resource or the community.
  3. Under Device IDs for Remote Open, enter one or more IDs, for example Main-door-1. anny suggests already used IDs for selection.
  4. For booking rules, define how long the Access before the booking and the Access after the booking should apply.
  5. Save the rule.
  6. Activate the integration via the toggle in the top right.
Once the integration is active, anny automatically creates access rights with an open button for matching bookings and community memberships.
Test the connection with your own test booking on the affected resource. Open the booking, click Unlock lock and check whether your system receives the request.

​
Settings & options

There is no switch for remote opening here. With Custom Remote Open it is always active, because the integration knows no other access method. You edit or delete existing rules via the three dots. Under Access through communities, you also find the action Create missing access rights for existing community members. This supplies members who joined the community before the rule.

​
Remote Open

With Remote Open, customers open a shared device at the push of a button, without an app and without an account at the locking system. The button appears as soon as the access right is valid and disappears after the period ends. As an admin user, you open the same device in the booking details via Unlock lock. Access from a community applies permanently and has no end date.

​
Limitations

The Custom Remote Open integration does not support:
  • Device detection: anny does not retrieve a device list. You enter the device IDs by hand and have to assign them in your system yourself.
  • Status query: anny does not know whether a door is open or closed. Only the opening request is sent.
  • Other access methods: there is no PIN code, no QR code, no access link and no provider app. Without an open button there is no access.
  • Automatic retry: if an opening fails, anny does not try again. Customers have to press the button once more.
  • Multiple booking rules per resource: each resource may appear in only one booking rule, otherwise the rule cannot be saved.
  • Access without a customer: internal blockers and not yet accepted bookings receive no access right.
All requests of a connection go to the same endpoint URL and use the same token. The distinction between multiple devices runs exclusively via the passed device ID.

​
Disconnect

If you want to keep the existing access rights but stop new ones from being created, deactivate the integration. If everything should be reset and deleted, delete the integration. In your own system, you do not have to undo anything afterwards, because anny stores no authorizations there.
You can do both under Integrations: deactivate via the toggle in the top right, delete via the three dots → Delete.

​
FAQ

Any system that can be opened via its own interface. anny only sends a request to your endpoint URL. You control the actual opening yourself, for example via the control of your door, gate or barrier.
You assign them yourself. anny passes the entered ID unchanged to your endpoint. Choose descriptive IDs like Main-door-1, because customers see the ID in the booking as the name of the door lock.
No. The button appears in the anny app, in the browser and via the link in the booking confirmation. An account at the locking system is not needed.
anny removes the access right as soon as the cancellation is processed. The open button disappears with it. A response to your system is not needed, because no authorization was stored there.
Click Regenerate token and copy the new token directly from the window. The old token no longer applies from that moment. Store the new token in your system immediately, otherwise all openings fail.

​
Troubleshooting

Usually there is no valid access right. Check whether the integration is active, whether a rule covers the booked resource and whether the booking was accepted. Then check the access period in the booking details, because outside of it the button cannot be used.
Your endpoint did not respond to the request successfully. Check whether the endpoint URL is correct and publicly reachable and whether it starts with https://. Also check whether the token stored in your system still matches the current endpoint token.
For recurring bookings, anny schedules the access rights and creates them only shortly before the respective appointment. In the booking details, the access stays at Scheduled until then. This is not a bug, the button appears in time for the appointment.