Filters

Filters allow applications to refine the charging stations returned by the Tile Service API. Beyond simply hiding non-matching results, certain filters also transform the station data to ensure the response is contextually relevant.


How filters affect data

When a request includes filters, the Tile service performs two distinct operations:

  1. Exclusion of non-matching stationsAny station that does not meet the specified filtering criteria is removed from the response entirely. This operation occurs when station-level filters or EVSE-level filters are used.
  2. Data transformationWhen particular filtering parameters are provided, the Tile Service recalculates some of the station’s dynamic properties. This operation occurs when EVSE-level filters are used.

Implementation

Filter parameters can be appended to the request URL as query strings to any of the Tile Service endpoints (MVT or JSON or Count). If no filters are applied, all available charging stations are returned, and no data transformations are done.

Tile URL
bash
https://api.chargetrip.io/v2/station/..../?{filter_1}&{filter_2}&{filter_n}

Levels

Filters can exist on two levels. EVSE level or station level. Each with their own impact and results as described below.

Station level

Filters that evaluate the station’s global attributes. These filters are exclusion-only: exclude non-matching stations but never modify the returned data fields.

amenities · enum ·

https://api.chargetrip.io/v2/station?preferred_operators=true

Filter to include only stations that provide the specified amenities.

Possible values

HOTELSHOPPINGBATHROOMSUPERMARKETPLAYGROUNDPHARMACYMUSEUMCOFFEERESTAURANT
preferred_operators · boolean ·

https://api.chargetrip.io/v2/station?preferred_operators=true

Filter to include only stations operated by operators configured as preferred. Preferred operators can be set in project settings within the dashboard.

Possible values

truefalse
truck_dedicated · boolean ·

https://api.chargetrip.io/v2/station?preferred_operators=true

Filter to include only stations dedicated or primarily intended for truck charging. Only applicable if the Eco-Movement station database is used; otherwise, it is ignored.

Possible values

truefalse

EVSE level

Filters that evaluate the station’s specific charging capabilities. These filters perform exclusion and transformation: non-matching stations are excluded, and matching stations have their dynamic fields recalculated.

connectors · enum ·

https://api.chargetrip.io/v2/station?preferred_operators=true

Filter to include only stations that have EVSEs with the specified connector types. Accepts an array of strings with any OCPI 2.2.1 connector values.

Possible values

CHADEMODOMESTIC_ADOMESTIC_BDOMESTIC_CDOMESTIC_DDOMESTIC_EDOMESTIC_FDOMESTIC_GDOMESTIC_HDOMESTIC_IDOMESTIC_JDOMESTIC_KDOMESTIC_LDOMESTIC_MDOMESTIC_NDOMESTIC_OIEC_60309_2_single_16IEC_60309_2_three_16IEC_60309_2_three_32IEC_60309_2_three_64IEC_62196_T1IEC_62196_T1_COMBOIEC_62196_T2IEC_62196_T2_COMBOIEC_62196_T3AIEC_62196_T3CPANTOGRAPH_BOTTOM_UPPANTOGRAPH_TOP_DOWNTESLA_RTESLA_SGB_TCHAOJINEMA_5_20NEMA_6_30NEMA_6_50NEMA_10_30NEMA_10_50NEMA_14_30NEMA_14_50

Examples

To display the behaviour, examples have been provided for filtering and data transformations below.

Filter examples

Filters can exist on two levels. EVSE level or station level. Each with their own impact and results as described below.

Same filter type, different values
Example URL
bash
https://api.chargetrip.io/v2/station?connectors[]=IEC_62196_T1_COMBO&connectors[]=CHADEMO
StationPropertiesMatches
A2x IEC_62196_T1_COMBO
1x CHAdeMO
1x TOILET
1x RESTAURANT

Matching reason

Has CHAdeMO charger
B1x IEC_62196_T1_COMBO
1x IEC_62196_T2_COMBO
1x RESTAURANT

Title

The description text
C2x IEC_62196_T2_COMBO
1x TOILET

Title

The description text
Multiple different filter types
Example URL
bash
https://api.chargetrip.io/v2/station?minimum_power=120&evse_statuses[]=AVAILABLE&connectors[]=IEC_62196_T1_COMBO
StationPropertiesMatches
A2x IEC_62196_T1_COMBO
1x CHAdeMO
1x TOILET
1x RESTAURANT

Title

The description text
B1x IEC_62196_T1_COMBO
1x IEC_62196_T2_COMBO
1x RESTAURANT

Title

The description text
C2x IEC_62196_T2_COMBO
1x TOILET

Title

The description text

Data transformation examples

Some outputs are recalculated when EVSE-Level filters are applied. These fields are “transformed” to ignore connectors that don’t match the user’s search criteria. These “dynamic” output fields are connector_maximum_power and evse_status_*.

Same filter type, different values The request includes CHADEMO connector filter. The station is included because it has a CHADEMO connector, but the dynamic fields are transformed to ignore the Combo Type 1 chargers.

Example URL
bash
https://api.chargetrip.io/v2/station?connectors[]=IEC_62196_T1_COMBO&connectors[]=CHADEMO
Response
json
{
    "id": "station_a",
    // Static: Remains 150 kW (This represents the station maximum power across all conectors)
    "station_maximum_power": 150,
    // Dynamic: Adjusted to 100 kW (Max power of the CHADEMO connector)
    "connector_maximum_power": 100,
    // Dynamic: Counts the 1 CHADEMO chargers
    "evse_status_out_of_order": 0
    // Dynamic: 0, because the charging Type 1 plugs are filtered out
    "evse_status_available": 1,
}
  • Getting started

    Get started with the Chargetrip API.

  • API reference

    Browse our api and endpoints.

  • Examples

    Explore examples and start building.

How filter works

The filter argument lets you narrow down results by passing an input object with specific criteria. Each field within the filter is optional — only include the ones relevant to your query.