JavaScript is disabled in your browser and Aparcalia needs it to work properly. Enable it for this page to work properly.

forgotten your password ? Sign In

All your parking needs online


 how to set your systems to publish real-time information of your parking


Warning: This page contains technical information

In the Car-park basic data section, there is a field entitled Url ping (see image).

Set the real-time information service for your parking

Enter a URL (eg http://maquina.dominio.aaa/ruta?param=b) where your occupancy level is defined according to the format below. Aparcalia will query this URL every time a user clicks on your parking to show your occupancy level. You may define your occupancy according to 3 different strategies as indicated below.

You should set your service to respond to a POST petition from our servers, as follows:

Content-Type: application/json
Charset: UTF-8
Content: It must answer an array of JSON objects with 3 properties each:

property 1) "f": Numeric field that indicates the date of data updating, measured in milliseconds since January 1, 1970, 00h: 00m: 00s GMT.
property 2) "pId": Alphanumeric field with your parking internal identifier, according to your nomenclature
property 3) "cual","cuant" ó "pct": Numeric field that indicates the number of free spaces

  1. Qualitative Indicator:
    It only shows a color sign indicating whether the parking is full or free.
    This is an example of the expected response from your systems (the example is formatted for readability; spaces are eliminated when in production):
    [
        {
            "f":1290614018569,
            "pId":"10",
            "cual":1
        }
    ]

    In this case, the parameter cual can take the values ​​0 or 1, meaning:
    0 -> full parking
    1 -> places available

  2. Quantitative Indicator:
    It shows a sign indicating whether the parking is full or, in case there are spaces, the number of free spaces
    This is an example of the expected response from your systems (the example is formatted for readability; spaces are eliminated when in production):
    [
        {
            "f":1290614018569,
            "pId":"10",
            "cuant":35
        }
    ]

    In this case, the parameter cuant can be any positive integer number, which indicates the number of free spaces.
    0 -> full parking
    3 -> 3 places available
    88 -> 88 places available

  3. Percentage Indicator:
    It shows a sign indicating whether the parking is full or, in case of free spaces, the percentage of occupancy
    This is an example of the expected response from your systems (the example is formatted for readability; spaces are eliminated when in production):
    [
        {
            "f":1290614018569,
            "pId":"10",
            "pct":0.14
        }
    ]

    In this case, the parameter pct can be any number between 0 and 1, indicating the percentage (in per one) of free spaces in the parking:
    0 -> full parking
    0.1 -> 10% of places available
    0.87 -> 87% of places available

If you have several car parks and you have configured a unique URL to provide the occupancy data for all of them, you can concatenate as many JSON objects as you want. Or you can even mix visualization strategies according to your interest.

When our servers receive an array with more than one JSON object (like the example below), we will show the information of that whose identifier (parameter pId ) matches the one you indicated in the Car-park basic data form.

[
    {
        "f":1290614018569,
        "pId":"PK1",
        "pct":0.14
    },
    {
        "f":1290614018569,
        "pId":"PK9",
        "cuant":28
    },..{}
]

Next you can see three sample images of how is the occupancy displayed depending on the strategy chosen:

  1. Qualitative:

    Real time occupancy for qualitative strategy


  2. Quantitative:

    Real time occupancy for quantitative strategy


  3. Percentage:

    Real time occupancy for percentage strategy