Release notes

✨ Improvements

• Improved dashboard security by introducing better token management

⚡️ New features

• Added support for amenity_preferences. Within the new argument, scheduled_charge_stops is introduced, which can be used to schedule a stop with a specific duration, amenity types and distance between the amenities and station. all_charge_stops replaces amenities and can be found within the same argument.

📦 Deprecations

• Deprecated amenities in favor of amenity_preferences. See deprecations for more information.

🐞 Bug fixes

• Fixed a bug on Route Steps where some route steps had a negative duration.

🐞 Bug fixes

• Fixed a bug on the station import where a large number of stations with changed coordinates would cause the import to fail.

✨ Improvements

• Improved stability by fixing various small bugs.

🐞 Bug fixes

• Fixed a bug on Isoline subscription where no update were send after the first two states.

🐞 Bug fixes

• Fixed a bug on the Tile Service where the map focused on incorrect coordinates after breaking up a cluster.

🐞 Bug fixes

• Fixed a bug where the SoC dropped after reaching a waypoint.
• Fixed a bug where the value 0 was skipped for cargo.

⚡️ New features

• Added support for connected car data platforms. For more information on vehicle connectivity please go here.

✨ Improvements

• Improved the user authorization service for operations that require authorization (review module, connect) by replacing the x-token header with Authorization.

🐞 Bug fixes

• Fixed a bug where stations with changing coordinates were not synchronised immediately after a station import.

⚡️ New features

• Added support for the crossborder route step to indicate when a route crosses a border.

🐞 Bug fixes

• Various small bug fixes.

🐞 Bug fixes

• Fixed a bug where we did not send a verification email after updating an account’s email address.
• Changed locations_data to location_data on updateNavigation mutation.

🐞 Bug fixes

• Fixed a bug where Isoline subscription was not shown in the schema

⚡️ New features

• Added support for the new query Isoline that offers a graphical visualization of the range of a vehicle based on energy consumption

✨ Improvements

• Improved schema descriptions for updateNavigation

🐞 Bug fixes

• Fixed a bug with missing country codes on country_code GraphQL enum

✨ Improvements

• Improved stability by restructuring our backend services.

🐞 Bug fixes

• Fixed a bug where in some cases, the total load in the car was not taken into account when establishing the rangeStart of the alternative routes

✨ Improvements

• Improved stability by fixing various small bugs.

✨ Improvements

• Improved our security by enforcing newly created projects to send an x-app-id, together with the x-client-id. You can either use the default app-id, or create one yourself. If you are an existing customer, we will get in touch with you about this security measure.
• Improved the schema description for finalStateOfCharge
• Improved the schema descriptions for plugsAvailable, plugsOccupied, plugsUnknown, plugsOutOfOrder and plugsCount.

🐞 Bug fixes

• Fixed a bug where the name value for stationVia came from the database instead of the newRoute mutation.
• Fixed a bug where some data within custom_properties was missing for stations of 22 kW and below.

✨ Improvements

• Improved our security by enforcing newly created projects to send an x-app-id, together with the x-client-id. You can either use the default app-id, or create one yourself. If you are an existing customer, we will get in touch with you about this security measure.
• Improved the schema description for finalStateOfCharge
• Improved the schema descriptions for plugsAvailable, plugsOccupied, plugsUnknown, plugsOutOfOrder and plugsCount.

🐞 Bug fixes

• Fixed a bug where the name value for stationVia came from the database instead of the newRoute mutation.
• Fixed a bug where some data within custom_properties was missing for stations of 22 kW and below.

✨ Improvements

• Improved the way we handle requests by introducing an automatic retry system to prevent updates to our Graph Engine to interfere with route requests.

🐞 Bug fixes

• Fixed a bug where the distance traveled on a ferry was not correctly added to the total distance traveled.

⚡️ New features

• Added the ability to add and update cargo or occupants at the origin, via points and destination. Read more here.
• Added missing station data to our station operations.

✨ Improvements

• Improved error message when the final state of charge was over 80% of the vehicles battery capacity.

🐞 Bug fixes

• Fixed a bug where route.ev.cargo was not exposed.
• Fixed a bug where the client config for tile max zoom level was not used.

⚡️ New features

• Added connect to the car, carList and carPremium queries. Chargetrip is even more powerful when connected to telemetry data. Therefore, you can now request the connected car platforms that are supported per vehicle.

✨ Improvements

• Improved the performance of the stationStats query

🐞 Bug fixes

• Fixed a bug where we did not expose max_electric_power on the car query
• Fixed a bug where if the user did not send the State of Charge, the value from the battery capacity was used instead of defaulting to 100% State of Charge

⚡️ New features

• Added support for exposing the state of charge on routePath and pathPlot.

🐞 Bug fixes

• Fixed a bug where if the first stop was a via, the station id inside the leg field was an empty string instead of null.
• Fixed a bug on navigation where a route without charges included the feature point of the destination on next_station.
• Fixed a bug where the polyline for legs and steps of a route was missing the final point.

⚡️ New features

• Added type walking to RouteStep to easily identify if the origin, via or destination is unreachable by car.

✨ Improvements

• Improved the stationAround and stationList queries by extending them with the following filters: Power, PowerGroups, Connectors or ConnectorType, AvailableOnly, PreferredOperator.
• Improved the stationAround and stationList queries by allowing to search over amenities and properties.
• Improved route mutation validation by including an error when the finalStateOfCharge exceeds 80% of the capacity.

🐞 Bug fixes

• Fixed a bug on toll roads where the API did not expose the RouteStep type toll
• Fixed the schema description on capacity

⚡️ New features

• Added support for exporting the Tile Service as a JSON response, allowing you to display the response on the mapping provider of your choice. An example can be found over here.

✨ Improvements

• Improved the file size of our images by switching to a new image compressor.

🐞 Bug fixes

• Fixed a bug on error code CLIENT_AUTH_MANDATORY where it used to extend with HttpNotAllowed instead of the correct HttpForbidden.

🐞 Bug fixes

• Fixed a bug on the desired final state of charge of the battery, where the actual final state of charge did not match the provided final state of charge.

⚡️ New features

• Added the new query navigation and included new mutations to update and recalculate a navigation session. Read more here.

✨ Improvements

• Improved our validation of route mutations by enforcing the error when SoC is 0 or a negative value.

🐞 Bug fixes

• Fixed a bug on via points, were optimisation rules were causing routes to fail in areas with a low density of stations.

⚡️ New features

• Added the new navigation query and included new mutations to update and recalculate a navigation session. Read more here.

✨ Improvements

• Improved the performance of the tile service

🐞 Bug fixes

• Fixed a bug where route steps on legs had undefined ids.
• Fixed a bug where route steps were shown as an empty array.
• Fixed a bug where the polyline on route steps was an empty string.
• Fixed a bug were the polyline on the leg was an empty string.

⚡️ New features

• Improved stability by fixing various small bugs

🐞 Bug fixes

• Fixed a bug on station stats for new projects; now station stats are directly available after the creation of a new project

⚡️ New features

• Added the app id in the response
• Added an error message for an incorrect app id

🐞 Bug fixes

• Fixed a bug on station stats for new projects; now station stats are directly available after the creation of a new project

✨ Improvements

• Improved the scheme descriptions for fast_charging_support
• Improved stability by fixing various small bugs

🐞 Bug fixes

• Fixed a bug in routing with OCPI-status BLOCKED. Status BLOCKED is no longer taken into account.

⚡️ New features

• Added support for external ids on via points

✨ Improvements

• Improved stability by fixing various small bugs

⚡️ New features

• Added route steps to easily identify road characteristics like toll and ferries.
• Added support for OCPI 2.2.1

✨ Improvements

• Improved performance when creating a new client or updating cars.

⚡️ New features

• Added the ability to manually flag road closures. We can manually close roads permanently or for a date range in regions where road closure data is seasonal or not available through traffic and incident API's.

🐞 Bug fixes

• Fixed a bug in routing that caused the engine to consider the entry and exit ramp over the highway itself.

⚡️ New features

• Added support for the Eco-movement pricing module. All our customers using the pre integrated Eco-movement database, can use pricing instead of tariff on EVSEs. We recommend customers to switch to the new pricing query. See pricing for more information.
• Added operatorName and operatorRanking on routeLeg

🐞 Bug fixes

• Fixed a bug in stationStats on the stations count grouped by amenities.

⚡️ New features

• Added the new query navigationMapping that converts a route to navigation instructions for a specified mapping provider. Currently Mapbox is supported, other mapping providers will follow.
• Added an all new dark and light mode to the dashboard.
• Added date range inputfields to the dashboard calendar dropdown.
• Added the ability to remove your account from the dashboard.
• Added the ability to remove your own projects from the dashboard.

✨ Improvements

• Improved stability by fixing various small bugs

⚡️ New features

• Added operator ranking to bestMatching type. The best matching route is now a combination of operator and amenity preferences.

⚡️ New features

• Added support for the graphql-transport-ws protocol on our WebSocket. Learn more.

📦 Deprecations

• Deprecated passengers in favor of occupants. See deprecations for more information.

✨ Improvements

• Improved state management on the dashboard to remember filter and search states while navigating through pages.
• Improved the performance of fetching project details.

🐞 Bug fixes

• Fixed a bug on the dashboard where you were not able to enter certain domains as HTTP referrer.
• Fixed a bug on the dashboard where an empty graph would sometimes scale on Firefox.

✨ Improvements

• Improved stability by fixing various small bugs.

✨ Improvements

• Improved the station import by comparing old and new station data before adding or removing stations from the database.

🐞 Bug fixes

• Fixed a bug on alternative routes where an error message was thrown when tariffs were requested.

⚡️ New features

• Added the ability in the dashboard to prioritize operators on a project / x-client-id.

🐞 Bug fixes

• Fixed a bug where the safeRiskMargin caused routes to fail when the SoC at origin was below the safeRiskMargin.

⚡️ New features

• Added the ability to automatically add cars to a project / x-client-id. Note: when enabled only new cars will be added. Cars that are currently available and not attached to a client will not be added.
• Added the ability to set charge mode on a project / x-client-id
• Added the ability to set charge stop duration on a project / x-client-id

⏭ Onto the next one

• In this release we honor Jay-Z. No new features, improvements or fixes. We are on to the next one.

⚡️ New features

• Added the ability to restrict the use of client and application ids based on different security restrictions per platform. Read more here.
• Added the ability to configure x-app-id security restrictions on the dashboard
• Added the ability to customize the charge duration and charge mode on the x-client-id through the dashboard

🛠 Refactoring

• Some refactoring under the hood that needed to be launched.

⚡️ New features

• Added the ability to query range in percentages on getRoute and use percentages as an input value. Please be aware when adding percentages for the state of charge and the final state of charge they are a percentage of the usableCarBattery or the capacity when including this object in the mutation.

✨ Improvements

• Improved search and filtering on the operatorList query.

🐞 Bug fixes

• Fixed an issue where rangeEnd and rangeEndKwh were 0 when plotting a route using a car that does not support fast charging.

✨ Improvements

• Improved error handling on the login section of the dashboard.

🐞 Bug fixes

• Fixed a bug where station.review.count and station.review.rating were not incremented when a review was added.

✨ Improvements

• Improved stability through several software updates.

✨ Improvements

• Improved error coverage for the route mutation validation. All errors are currently collected and used to improve the error messages. Routes will be returned for now, even if there are mistakes in the route mutation. We will notify you before enforcing the new errors.

🐞 Bug fixes

• Fixed a bug where safeRiskMargin was applied twice in winter scenarios.

👉 My finger ... is on the button

✨ Improvements

• Improved stability through several software updates.

🐞 Bug fixes

• Fixed a bug where an incorrect start range when using OPTIMIZE_TRAVEL_TIME was displayed.

✨ Improvements

• Improved tile service cluster break-up by adjusting the expansion zoom calculation.
• Improved filtering of stations by excluding onboard chargers below 20 kW for all models with onboard capabilities higher than 20 kW.

🐞 Bug fixes

• Fixed a bug where the routePath query changed the route path location search from a strict find to nearest point search.
• Fixed a bug where list queries accepted negative integers.

⚡️ New features

• Added the input argument operators to the newRoute mutation! We are happy to announce the release of a tiered preferred operator system and the ability to exclude operators from routing! From now on, in your route request, you will be able to add what operators you want us to prefer in order of ranking, and let us know if there are operators you wish to exclude from the route calculation! The same functionality is possible to include in the config of your client ID, which will soon be possible to adjust in the dashboard; get in touch with us directly until then.

✨ Improvements

• Improved charge time estimates by introducing a generalized charge curve model that accounts for the On Board Charging (OBC) power threshold and drop-off characteristic at higher state of charges. The generalized charge curve model is used for all cars for which we have sufficient data. We will increase our coverage over time when more data becomes available.

✨ Improvements

• Improved release times by lowering the memory usage on our end to end tests.
• Improved performance for several sections of the Chargetrip dashboard.

🐞 Bug fixes

• Fixed an issue with the optimal route where in some cases a station was selected far from the optimal route.

⚡️ New features

• Added chargeMode. This field can be set to OPTIMIZE_TRAVEL_TIME and ALWAYS_TO_MAX_CHARGE.

✨ Improvements

• Improved CI/CD for faster releases.

⚡️ New features

• Added 'raw' turn-by-turn instructions that can be used in combination with navigation SDK's to offer turn-by-turn navigation. To receive the instructions, add the instructions argument to the newRoute mutation. Don’t forget to also request the instructions in the getRoute request. Important: this feature is still in active development and it should only be used for test purposes until further notice.

✨ Improvements

• Improved performance for several sections of the Chargetrip dashboard.

⚡️ New features

• Added the field max_electric_power which gives the maximum electric power in kW of a connector/adapter. max_electric_power is exposed on the carList, Car and CarPremium query.
• Added the ability to configure the time it takes to halt, start and stop charging on client level. We default to 5 minutes if you choose not to change this. This functionality will soon become available to you in the dashboard.

✨ Improvements

• Improved the description of the power field for connectors and adapters to: "Usable electric power in kW".

🐞️ Bug fixes

• Fixed an issue where the route mutation returned an internal server error when the operatorPrefer parameter was set to true and the operatorIds parameter set to null.
• Fixed an issue where safeRiskMargin could be set to null. An integer between 0 and 60 is now required.

✨ Improvements

• Improved stability through several software updates.

⚡️ New features

• Added configurable charge speed for our customers. By default we use the average charge speed, but customers can now choose to use the maximum charge speed instead. This functionality will soon become available to you in the dashboard.

🐞️ Bug fixes

• Fixed an issue with the tariffs module where in some cases the wrong tariff was displayed.
• Fixed an issue when the WebSocket broke and it didn’t return a result on a subscription by adding a KeepAlive message.

✨ Improvements

• Improved the performance of our Tile Service to provide more structured clustering and faster response times.

⚡️ New features

• Added the ability to change your Chargetrip account password through your profile.

✨ Improvements

• Improved performance for several sections of the Chargetrip dashboard.

⚡️ New features

• Added the pathPlot property in favour of elevationPlot.
• Added support to search the carList by id.

✨ Improvements

• Improved how routes should be queried. A single additional route query is no longer needed after you started a route subscription.

🐞️ Bug fixes

• Removed the unused operator and station subscriptions.
• Fixed an issue where in some cases an incorrect connector type was selected at charge stations.

⚡️ New features

• Added support for URL parameter authentication on top of header authentication to provide a more seamless Mapbox integration. See our updated documentation here.

✨ Improvements

• Improved our calculations in regions where the density of stations is still low by widening our search for possible stations if the first route fails.

⚡️ New features

• Chargetrip's Graph Engine has been rebuild from the ground-up to maintain performance and withstand higher loads. The new version of the engine calculates routes faster, uses more variables and gives back better results.

✨ Improvements

• Improved the client environment's stability by moving the import and processing of station data outside the client environment.
• Improved route calculation speeds when searching for stations along a route.
• Improved route calculation speeds when using preferred operators.
• Improved car data processing.

⚡️ New features

• Added pagination to the carList query.
• Added search over naming.make, naming.model, naming.chargetrip_version to the carList query.
• Added filter for availability to the carList query.

✨ Improvements

• Improved car data structuring which allows for better clustering and query scalability.

🐞️ Bug fixes

• Fixed a bug that prevented using stations as via point.

✨ Improvements

• Improved car data clustering. Fields are now categorized by using nesting.

⚡️ New features

• Station data has been extended and now includes historical station availability.

🐞️ Bug fixes

• Fixed a bug where error codes were not consistent.

🐞️ Bug fixes

• Fixed a bug that hid 24 / 7 information for some stations.
• Fixed a bug where alternative routes with a single charge were not displayed correctly.

⚡️ New features

• Added the chargetripRange field.

✨ Improvements

• Migrated fields from the carList query to the car query to allow caching of the carList query.

🐞️ Bug fixes

• Fixed a bug where the number of amenities were not equal when comparing between the stationList and amenityList.

✨ Improvements

• Improved outside temperature model which enhances the route computation speed and improves the charge stop accuracy.
• Various other improvements to improve our route calculation speed.

🐞️ Bug fixes

• Fixed a bug where the ordering of alternative routes was wrong.

⚡️ New features

• Added custom error codes and detailed error descriptions. No more guess-work.

🐞️ Bug fixes

• Various small bug fixes.

✨ Improvements

• Improved the description of our recently released chargetripEdition field.
• Improved various chargetripEdition field names to be more descriptive.

🐞️ Bug fixes

• Fixed a bug where via points were not correctly added to the route.

⚡️ New features

• Added the chargetripEdition field.

🐞️ Bug fixes

• Fixed a spelling mistake by renaming recommandedSpeed to recommendedSpeed.
• Fixed the destination type from stationVia to stationFinal when adding a station as final destination.

⚡️ New features

• Added the ability to request alternative stations along an existing route.
• Added the ability to set charge stations as waypoints to an existing route.

🐞️ Bug fixes

• Renamed the stationAlong field to stationsAlongRoute.

⚡️ New features

• Added support for selecting different power filters.
• Added support to select all available connectors.

🐞️ Bug fixes

• Fixed various spelling mistakes and inconsistencies in our documentation.

⚡️ New features

• Added support for OCPI 2.2. OCPI specifications can be found here. The full specifications can be found here.

⚡️ New features

• Added an exclusive Eco-Movement integration.
• Added support for OCPI 2.1.1

🐞️ Bug fixes

• Fixed various spelling mistakes and inconsistencies in our documentation.
• Fixed missing descriptions for all types that return values with a unit.

⚡️ New features

• Added support for Peugeot e-208 and Seat Mii Electric.
• Added support for the OCPI Tarrif Module. More information about the OCPI 2.1.1 specifications can be found here. The full specifications can be found here.

🐞️ Bug fixes

• Fixed various spelling mistakes and inconsistencies in our documentation.