Barriers (Came / FAAC)
Guests drive in, the camera or RFID reader recognises their plate, the barrier opens. No staff at the gate. CampOne handles the allowlist: when a booking is confirmed with a licence plate, the plate is registered with the barrier provider for the booking dates; on check-out, it’s removed.
The adapter supports Came and FAAC out of the box and is structured so a third vendor can be added without rewriting the booking integration.
What it gives you
Section titled “What it gives you”- Auto-registration on
Booking → CONFIRMED(when a licence plate is captured) - Auto-deregistration on
Booking → COMPLETED - Inbound webhook for pass / transit events from the barrier (signed with HMAC-SHA256)
- Audit log of every registration / deregistration / event
Prerequisites
Section titled “Prerequisites”Both Came and FAAC are partner / OEM programs — you don’t self-register API access. Submit a partnership request:
- Came Connect: https://www.came.com/global/en/contact-us/ — ask to be routed to Came Svizzera
- FAAC eBoard / J-Track: call +39 051 61724 (FAAC HQ Bologna) — they don’t run a public developer program; integration access is per-installer
You’ll need:
- The provider’s API base URL (different per vendor)
- API credentials in the provider’s auth scheme (often a JSON blob — Came uses OAuth, FAAC uses an
X-Api-Key) - A
gate_id/ installation ID - Webhook signing secret (if the barrier pushes pass events to CampOne)
What you’ll paste into CampOne
Section titled “What you’ll paste into CampOne”Settings → Integrations → Vendor Adapters → Schranken:
| Field | Description |
|---|---|
| Provider | Came, FAAC, or Other |
| Environment | Test / Production |
| Endpoint | The provider’s API base URL |
| Gate ID | Your installation identifier on the provider side |
| Allowlist format | License plate or RFID tag — whichever your hardware reads |
| API credentials | JSON blob containing whatever the provider needs ({"client_id": "…", "client_secret": "…"} for Came; {"api_key": "…"} for FAAC) |
Click Save, then Test connection. The probe calls the provider’s “recent passes” endpoint — green pill confirms.
Capturing the licence plate
Section titled “Capturing the licence plate”The licence plate field appears on the booking creation form (next to nationality). Operators can also leave it blank — the Schranken hooks silently no-op when there’s no plate, so the rest of the booking flow is unaffected.
Pass events
Section titled “Pass events”If the provider supports outbound webhooks, configure CampOne’s webhook URL on their side. The endpoint is publicly reachable but signature-verified — without the correct HMAC header, requests are rejected. Pass events are stored in the integration log so you can audit who entered when.
Adding a new barrier vendor
Section titled “Adding a new barrier vendor”The adapter has an internal BarrierProvider abstraction. Adding a third vendor (e.g. Nice) is a one-file change in services/providers.py — talk to your integration partner if you have a different barrier on site.
Support contacts
Section titled “Support contacts”| Vendor | Contact |
|---|---|
| Came | https://www.came.com/global/en/contact-us/ |
| FAAC | +39 051 61724 (Bologna HQ) · https://www.faac.biz/contacts |
Limitations
Section titled “Limitations”- Came Connect and FAAC eBoard documentation is partially closed; both adapters use best-effort REST paths that may need adjustment when the vendor confirms the exact endpoints. We’ve kept the seam tight so a one-line fix lands the change.
- The licence plate is captured at booking creation time. If a guest swaps cars on arrival, you’ll need to update the plate on the booking, which will deregister the old plate and register the new one.