Connect Inrange Without Constraints

The Inrange connector is built and maintained by IntelliPaaS against the Inrange Pins API, authenticating with a facility-scoped API key and addressing each venue by its own Inrange facility ID, with separate production and sandbox endpoints for safe testing. When a booking is created — or its start or end time changes — the connector requests a PIN for the bay and writes it back to the booking record, valid until the session ends. Not every booked asset needs one, so the connector only calls Inrange for the assets a venue has flagged, keeping trainer and equipment bookings out of the flow. Built originally alongside our ROLLER adapter, it closes the gap between the moment a guest books and the moment they walk up to the bay.

Inrange integration capabilities

• →Generate a bay access PIN when a booking is created, scoped to the venue's Inrange facility ID.
• →Re-issue the PIN automatically when a booking's start or end time changes.
• →Derive single-player or multiplayer mode from the booking quantity.
• →Pass player name and email through from the booking's customer record.
• →Store the returned PIN and PIN identifier on the booking for later revocation.
• →Capture the Inrange status code and error message per booking for reconciliation.

These capabilities remove the manual step between a confirmed booking and a guest being able to play, eliminating the front-desk lookups and re-issued codes that slow arrival at busy venues. IntelliPaaS handles facility resolution, play-mode derivation and error capture automatically, so venue teams get a working PIN on the booking without touching Inrange directly.

Common integration scenarios

• →Issue a bay PIN automatically when a guest books a range session in ROLLER.
• →Refresh the PIN when a booking is rescheduled, so the old code expires with the old slot.
• →Include the PIN in confirmation emails and SMS via your messaging platform.
• →Restrict PIN generation to bookable bay assets, excluding trainers and equipment.
• →Report failed provisioning attempts so venue staff can act before the guest arrives.

These scenarios address the friction that sits between a venue's booking system and the technology on the range itself — guests arriving without a code, rescheduled sessions leaving stale PINs active, and failed provisioning discovered only when someone complains at the desk — by automating the flow from booking to bay.

Deployment & security

Flexible deployment is essential for venue operators running estates across multiple sites and jurisdictions. IntelliPaaS supports private cloud and on-premise deployments with full regional data sovereignty, and the connector addresses each site by its own Inrange facility ID so a single integration serves a whole estate. All deployment modes receive the same feature set, connector library and support tier, with no capability trade-offs based on deployment choice.

Why IntelliPaaS

• →No-code to pro-code flexibility for all integration needs.
• →End-to-end security with facility-scoped API key authentication held in the IntelliPaaS secret store.
• →Multi-site ready, with per-venue facility resolution from a single integration.
• →Enterprise-grade observability with monitoring, alerting and audit logging.

Frequently connected apps

ROLLERSquareStripePayPalSalesforceTwilioMicrosoft TeamsSlackXeroPower BI