Determine the correct technical path to reach EVgo or Electrify America charging stations in a roaming or aggregator app, given neither operates its own public developer API

Steps

1. Recognize that EVgo and Electrify America function as eMSPs/network operators but contract their charge point management technology to underlying CPO software providers, so there is no single public 'EVgo API' or 'Electrify America API' to integrate against directly.
2. For station location/status data, integrate via the Alternative Fuels Data Center's station database (which both networks report into) or an aggregator (e.g. Open Charge Map, PlugShare) that already ingests their locations, rather than seeking a network-specific feed.
3. For roaming/charging-initiation access, pursue the OCPI-based interoperability agreements each network has established (e.g. the EVgo-Electrify America interoperability agreement, and each network's separate bilateral agreements with other CPOs/eMSPs like ChargePoint, EV Connect, SemaConnect) rather than a direct integration request as a new unaffiliated party.
4. Where a roaming hub (Gireve, Hubject) already has one of these networks or their technology partner connected, prefer joining through the hub over pursuing a point-to-point agreement, since that mirrors how existing interoperability deals were structured.
5. Budget for a business-development/partnership process (contracts, compliance review) rather than a self-serve API-key signup, since access to initiate charging on these networks is gated by commercial agreement, not open registration.