# Ionage > Integration guides and API references for the Ionage EV charging and fleet platforms - [Ionage API documentation](https://docs.ionage.in/index.md): Integration guides and API references for the Ionage EV charging platform - [Choosing an API](https://docs.ionage.in/guides/choosing-an-api.md): How the Nexus and FLO Partner APIs differ - [Nexus Partner API](https://docs.ionage.in/guides/nexus/overview.md): Access to charging stations, chargers, connectors, tariffs, customers, and charging sessions for partner backend integrations - [Authentication](https://docs.ionage.in/guides/nexus/authentication.md): Every Nexus API request must carry a valid API key - [Identifiers](https://docs.ionage.in/guides/nexus/identifiers.md): How Nexus resources are addressed in paths and responses - [Pagination](https://docs.ionage.in/guides/nexus/pagination.md): Paging through Nexus collection endpoints - [FLO Partner API](https://docs.ionage.in/guides/flo/overview.md): Fleet-scoped API for operations dashboards, driver apps, and backend-for-frontend integrations - [Authentication](https://docs.ionage.in/guides/flo/authentication.md): Every FLO Partner API request carries a fleet-scoped API key - [Identifiers](https://docs.ionage.in/guides/flo/identifiers.md): Prefixed opaque IDs and how to store them - [Idempotency](https://docs.ionage.in/guides/flo/idempotency.md): Safely retrying mutating FLO Partner API requests - [Pagination](https://docs.ionage.in/guides/flo/pagination.md): Paging through FLO Partner API collection endpoints - [List stations](https://docs.ionage.in/nexus-api/stations/list-stations.md) - [Get station](https://docs.ionage.in/nexus-api/stations/get-station.md) - [List tariffs](https://docs.ionage.in/nexus-api/tariffs/list-tariffs.md) - [Get tariff](https://docs.ionage.in/nexus-api/tariffs/get-tariff.md) - [List customers](https://docs.ionage.in/nexus-api/customers/list-customers.md) - [Get customer](https://docs.ionage.in/nexus-api/customers/get-customer.md) - [Upsert customer](https://docs.ionage.in/nexus-api/customers/upsert-customer.md): Creates the customer if the ID is new (201), otherwise replaces its optional fields (200). The request body is optional; an empty body creates a minimal customer, or clears name, phone_number, and email on an existing one. Use PATCH to change individual fields. - [Patch customer](https://docs.ionage.in/nexus-api/customers/patch-customer.md): Partially updates a customer. Only fields present in the request body are modified; absent fields are left unchanged. To clear an optional field, send an empty string. - [List sessions](https://docs.ionage.in/nexus-api/sessions/list-sessions.md): Returns charging sessions linked to customers. Sessions that cannot be associated with a customer are excluded. - [Start session](https://docs.ionage.in/nexus-api/sessions/start-session.md): Starts a charging session remotely. The request validates the station, charger, connector, and connector availability. If the supplied customerId does not exist, the API creates a minimal customer record before sending a start command to the charger. Optional auth_reference lets callers correlate th… - [Stop session](https://docs.ionage.in/nexus-api/sessions/stop-session.md): Stops an active charging session remotely. The request validates that the session exists, is linked to a customer, and is active before sending a stop command to the charger. A 200 response means the command was accepted for delivery; it does not confirm that charging has stopped. - [Get session](https://docs.ionage.in/nexus-api/sessions/get-session.md): Returns a single charging session by session ID. Returns 404 if the session does not exist or is not linked to a customer. - [Get charger](https://docs.ionage.in/nexus-api/chargers/get-charger.md) - [Get connector](https://docs.ionage.in/nexus-api/connectors/get-connector.md) - [List stations for an operator](https://docs.ionage.in/flo-api/operators/list-stations-for-an-operator.md) - [Get operator details](https://docs.ionage.in/flo-api/operators/get-operator-details.md) - [List operators available to the fleet](https://docs.ionage.in/flo-api/operators/list-operators-available-to-the-fleet.md) - [Get fleet driver](https://docs.ionage.in/flo-api/drivers/get-fleet-driver.md) - [Offboard a fleet driver](https://docs.ionage.in/flo-api/drivers/offboard-a-fleet-driver.md): Offboards the driver from fleet charging while retaining historical sessions. - [Update a fleet driver](https://docs.ionage.in/flo-api/drivers/update-a-fleet-driver.md) - [List fleet drivers](https://docs.ionage.in/flo-api/drivers/list-fleet-drivers.md) - [Onboard an app-charging driver](https://docs.ionage.in/flo-api/drivers/onboard-an-app-charging-driver.md): Creates a fleet driver who can use partner-initiated charging. The request fails without creating the driver if onboarding cannot be completed. - [Get fleet vehicle](https://docs.ionage.in/flo-api/vehicles/get-fleet-vehicle.md) - [Offboard a fleet vehicle](https://docs.ionage.in/flo-api/vehicles/offboard-a-fleet-vehicle.md) - [List fleet vehicles](https://docs.ionage.in/flo-api/vehicles/list-fleet-vehicles.md) - [Add a fleet vehicle](https://docs.ionage.in/flo-api/vehicles/add-a-fleet-vehicle.md): Normalizes the registration number and creates a fleet vehicle record. - [Get charging restriction](https://docs.ionage.in/flo-api/restrictions/get-charging-restriction.md) - [Replace charging restriction](https://docs.ionage.in/flo-api/restrictions/replace-charging-restriction.md): Replaces the full restriction. The update applies to future authorizations immediately and to already-active sessions through the restriction reconciliation worker. - [Delete charging restriction](https://docs.ionage.in/flo-api/restrictions/delete-charging-restriction.md) - [List charging restrictions](https://docs.ionage.in/flo-api/restrictions/list-charging-restrictions.md) - [Create charging restrictions](https://docs.ionage.in/flo-api/restrictions/create-charging-restrictions.md): Creates one or more connector-scoped charging restrictions. The request is atomic; if any item is invalid, no restrictions are created. In V1, every restriction item must include connector_id and exactly one subject identifier. soc_limit and time_ranges are optional. - [Get a charging station](https://docs.ionage.in/flo-api/stations/get-a-charging-station.md) - [List charging stations available to the fleet](https://docs.ionage.in/flo-api/stations/list-charging-stations-available-to-the-fleet.md): Latitude and longitude must be provided together. Radius can be supplied only with both coordinates. - [Get the fleet billing summary](https://docs.ionage.in/flo-api/billing/get-the-fleet-billing-summary.md) - [Get fleet payment transaction details](https://docs.ionage.in/flo-api/transactions/get-fleet-payment-transaction-details.md): Uses the same detail notation as the fleet dashboard and verifies that the transaction belongs to the authenticated fleet. - [List fleet payment transactions](https://docs.ionage.in/flo-api/transactions/list-fleet-payment-transactions.md): Uses the same field names and debit/credit notation as the fleet dashboard transaction feed. - [Request remote stop](https://docs.ionage.in/flo-api/sessions/request-remote-stop.md): Idempotently requests stop; an accepted request returns the session in TERMINATING state. - [Get the current charging-session state](https://docs.ionage.in/flo-api/sessions/get-the-current-charging-session-state.md) - [List fleet charging sessions](https://docs.ionage.in/flo-api/sessions/list-fleet-charging-sessions.md) - [Request a remote charging session](https://docs.ionage.in/flo-api/sessions/request-a-remote-charging-session.md): Validates the driver, connector, fleet contract, billing source, and restrictions before dispatching remote start. ## OpenAPI Specs - [flo-api-oas](/api-reference/flo/flo-api-oas.json) - [nexus-api-oas](/api-reference/nexus/nexus-api-oas.json) - [ocpi-hub-roaming-oas](/api-reference/ocpi/ocpi-hub-roaming-oas.yaml) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.