Discrepancy in Number of Chargers Between ABRP API Plan and Web Dashboard

Hi ABRP Team,

I'm currently integrating ABRP’s /v1/plan(

https://api.iternio.com/1/plan?destinations=…

) API into my application. When planning a route between two locations (e.g., San Francisco, CA to Kansas City, MO), I noticed a significant difference in the number of chargers(steps) returned by the API versus what is shown on the ABRP dashboard for the same route.

For example:

• ABRP Web Dashboard: 18 charging stops

• API Response (steps[] with is_charger = true): 32 entries

Each step has:

• is_charger = true

• charge_duration > 0

• charge_energy > 0

• Unique leg_id

Despite filtering steps with these fields, I still receive significantly more chargers than the actual charging stops used in the dashboard's route.

I need to limit the charging stations to only those actually used in the final plan, so I can send them as waypoints to mapping services like Google Maps (which has a 25-waypoint limit).

Questions:

1. Why does the API return more charger steps than shown in the ABRP route planner dashboard?

2. How can I programmatically extract only the chargers that ABRP actually uses in the plan, matching the dashboard?

3. Is there a specific field (e.g., leg_id, final, preferred, etc.) or another object (e.g., legs[]) that confirms the final selected charging stops?

Any clarification on this would be extremely helpful for using the API more efficiently and aligning results with what users see in the dashboard.

Thank you in advance!