How to connect Equinsa to Ronspot

---

The Ronspot–Equinsa integration provides a real-time access-control decision service that enables barriers, gates, or controlled entry points managed by Equinsa to validate whether a vehicle or cardholder is authorised to enter or exit a car park. In this architecture, Equinsa always acts as the initiating system. When a vehicle registration or card number is presented at a lane, the Equinsa controller sends a live request to Ronspot. Ronspot then evaluates the request against current booking data, user permissions and space availability, and returns an immediate authorisation decision.

In effect, Equinsa handles the on-site hardware and event detection, while Ronspot functions as the central authorisation engine. No data is pushed from Ronspot to Equinsa; all validation is performed at the moment of access, ensuring that any booking changes, cancellations, releases or updates are reflected instantly. This provides a secure, accurate and highly responsive method of controlling car park access based on Ronspot’s booking logic.

The endpoints described in this documentation allow Equinsa to submit registration or card-access queries and receive structured responses that determine whether access should be granted. This ensures seamless integration between the physical access equipment and Ronspot’s booking management platform.

Step 1: Log in to Ronspot admin panel

• Sign in to your Ronspot admin panel using your administrator credentials.

---

Step 2: Navigate to Account > Integrations

• In the left-hand menu, go to Account > Integrations 

---

Step 3: Add a new integration

1. Click  Add integration button at the top of the page.
2. In the pop-up window, choose Equinsa as the integration type.

---

Step 4: Configure the Equinsa integration

• You will be prompted to provide the following:
  • Name : Enter a name for the integration (e.g., Equinsa– Ronspot Integration)
  • Status:  Set to Active
    
• Press Save

---

Step 5: Associate your Ronspot zones

Next, you will specify which Ronspot zones should use the Equinsa integration.

• In the list of integrations, find your newly created Equinsa integration.
• Click the camera icon in the Actions column to manage zone associations.

---

Step 6: Add an association

• Click the Add association button at the top of the page.
• Select the Ronspot zone you want to link.
• Click Complete to save the association.
• Repeat this process to add more zone associations as needed.

---

Step 7: Copy the API access key

• Go back to the integrations list.

• Locate the Equinsa integration.

• Click the clipboard icon in the Actions column to copy your API access key.

You will need to send this to Equinsa.

---

Step 8: Provide the following details to Equinsa

Share the information below with your Equinsa technical contact so they can configure their system to call Ronspot’s validation endpoints.

1 - API Access Key

• Your unique API access key (copied in Step 7)

2 - Endpoint: Registration Access

Used to validate access based on vehicle registration number.

• Method: POST
• URL:

  • https://newapi.ronspot.ie/registration_access

• Headers

  • Content-Type: application/json
    apikey: Your API key

• Parameters

  • apikey (required): Your API key

  • parkingID (required): Parking facility ID — use 100 for testing

  • registration (required): Vehicle registration number

  • lane (required): "entry" or "exit"

  • time (optional): Timestamp; if omitted, the server applies the current time

• Example of JSON request:

  • {
       "apikey":"288d4022d050f98bc4320264d1b3f371", 
       "parkingID":"100",
       "registration": "EQY123",
       "lane":"entry",
       "time":""
    }

• Example of JSON response:

  • {
      "registration_access": {
          "registration": "EQY123"
      },
      "time": 1703245186,
      "lane": "entry",
      "result": {
         "know": true,        // The car registration exists in the Ronspot database
         "allowed": false,    // The employee currently has no active booking 
         "name": "John Doe",  // The employee’s name associated with the registration
         "space_number": null // No space number because there is no active booking
      }
    }

3 - Endpoint: Swipe Card Access

Used to validate parking access based on an employee’s swipe card number.

• Method: POST
• URL:

  • https://newapi.ronspot.ie/card_access

• Headers

  • Content-Type: application/json
    apikey: Your API key

• Parameters
  • apikey (required): Your API key
  • parkingID (required): Parking facility ID — use 100 for testing
  • card (required): Cardholder’s alphanumeric swipe card number
  • lane (required): "entry" or "exit"
  • time (optional): Timestamp; if omitted, the server applies the current time
• Example of JSON request :

  • {
      "apikey":"288d4022d050f98bc4320264d1b3f371",
      "parkingID":"100",
      "card": "ABCD12345",
      "lane":"entry",
      "time":""
    }

• Example of JSON response:

  • {
      "card_access": {
          "card": "ABCD12345"
      },
      "time": 1703245186,
      "lane": "entry",
      "result": {
          "know": true,        // The car registration exists in the Ronspot database
          "allowed": false,    // The employee currently has no active booking 
          "name": "Jane Doe",  // The employee’s name associated with the card
          "space_number": null // No space number because there is no active booking
      }
    }

 

If you need further help, please reach out at support@ronspotflexwork.com