All questions answered about our API. Learn about our cars, stations, routes, tile service modules.


    • We provide thumbnail and high-resolution files only. The client side is responsible for scaling the high-resolution image if needed.

    • Both wltp and chargetrip_range are estimates. WLTP is a testing cycle that car manufacturers use and their estimation is usually high. ChargetripRange comes from our own research. We recommend it, of course, but ultimately it’s up to you!

    • carPremium shows you all data we have on the cars in our database. It also allows you to cache this car data.

    • We have over 470 EVs in our database and are constantly adding more! You can find all the cars in our database here. You can also find the cars that we are expecting to add soon. Still missing a car? Be sure to let us know in the chat or via email.


    • Yes we are! We are currently using the OCPI 2.1.1 version

    • Yes. While our route calculates the best charging stations for you and your car — you can also view alternative stations. Simply add the stationsAlongRouteRadius flag to your newRoute mutation, and set the search radius in meters (the max is 5 km). Make sure to also add stationsAlongRoute to your route query. For more information, please see our documentation and examples.

    • Yes. We show an external ID next to the Chargetrip ID. You can find it under the external_id property. We receive this ID from an external data source.

      • Slow: < 43 kW

      • Fast: 43 kW - 150 kW

      • Turbo: 150 kW >

    • Unknown appears when we do not know the status of a charger. It could be free, busy or broken.

    • When calculating routes we only include chargers of 43 kW or more. This reduces charging time and thus creates faster routes.

    • You can find a list of all connectors in our schema, under OCPIConnectorType. The list updates when new connectors become available.

    • Yes! You can have up to 10 levels of preference. You also have the ability to exclude operators. Read more about this in our documentation and check out this example to try it yourself.

    • Charging station names flow from our station database. They receive these names either from the CPO itself or an intermediate party. Unfortunately, we’re not able to change the names of stations.


    • This depends on your particular use case, but we wrote an article about how you can add the basics in just three weeks!

    • Definitely. Just add alternatives to your route query, with all the parameters you want from your alternative routes.

    • A route calculated with the Chargetrip API can be exported to any navigation application. You must export the charging stations as waypoints. Google or similar navigation software will then display the charging stations as waypoints along the route.

    • When calculating your journey, we find chargers along the route to meet your desired final state of charge best. However, sometimes we are not able to find a station close enough to fulfill your request. For example, that can happen when chargers are too far away from the route.

    • There are different tools available online. In the examples, we use the Mapbox polyline package. It is essential to look at the order in which latitude and longitude are returned. In some cases, you might need to flip the coordinates before plotting them on your map.

    • No, this isn’t supported yet. But we’re working on it! In the meantime, you can show if a route had toll roads with route steps. Read more about this in our documentation.

    • You can add waypoints to your route by adding the via property to your route request. For more information, please take a look at our documentation.

    • We recommend that you subscribe to route updates, and unsubscribe when a route has reached a final status. For more information, consult our documentation and examples.

    • We do not take traffic into account when calculating routes. The impact of traffic on your consumption is minimal.

    • Yes, Chargetrip considers road closures. Most road closures are added automatically to OSM. We also offer the ability to add road closures manually. We can close a road permanently or for a specific date, for example, when a road is closed during winter. If you are still missing a road closure, please reach out to our support team.

Tile Service

    • Yes, this is possible! You can see how to use our Tile service with a different mapping provider in this example.

    • You can add a set of filters to the tile request. These filters are sent as query parameters. To request a tile you must have a combination of connectors and powers. For more information, refer to our examples and documentation.

White Label

    • We have a web white-label and a mobile white-label that runs on IOS and Android.

    • Together with our developers, we will add your branding and feel to the application. We can also configure operator preferences and much more.

    • You can go live within eight weeks from initial contact to launch. We will, of course, always be available for support.

Vehicle Connectivity

    • Chargetrip is data vendor agnostic and works with leading connected car and telemetry data providers. Connect currently comes pre-integrated with Enode, and we are actively working on integrating with more data providers.

    • Check out this page to view a complete list of vehicles available for Connect!

    • Great to hear that you’re interested in Chargetrip Connect. Drop us an email, and we will get you set up and ready to go!

    • We are data vendor agnostic and would love to learn more about your data provider to see how we could fit together. Please send us an email to learn more about our custom data integration flow.