> ## Documentation Index
> Fetch the complete documentation index at: https://api.corpay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Build fleet products that move faster with Corpay's Fleet API. This page gives you a quick overview of what is covered in the Fleet API reference.

## If you're building a fleet solution, portal, or backend

Fleet API part of the reference is centered around the operational building blocks you need to manage fleets in your own systems.

<CardGroup cols={2}>
  <Card title="Customers" icon="users">
    Create customer accounts (fleets), retrieve and update customer details, and manage customer status with block, unblock, and close actions.
  </Card>

  <Card title="Cards" icon="credit-card">
    Order, search, get card details, lodge, block/unblock, replace cards, request PIN reprints, cancel cards, and retrieve replaced card details.
  </Card>

  <Card title="Transactions" icon="receipt">
    Retrieve transaction history by customer or by card to power reporting, reconciliation, and operational tooling.
  </Card>

  <Card title="Master data and events" icon="database">
    Access reference data and review webhook payloads for card status changes, newly created cards, and replacement events.
  </Card>
</CardGroup>

## If you're building an EV driver app

The EV part of the reference helps you build driver-facing charging experiences, whether inside a dedicated EV app or as part of a broader fleet product.

<CardGroup cols={2}>
  <Card title="Charging locations" icon="map">
    Search and filter charging locations with Geosearch in a map area and retrieve detailed static and dynamic location data.
  </Card>

  <Card title="Charging sessions" icon="plug-circle-bolt">
    Start remote charging sessions, stop sessions, and retrieve session details so drivers can see live charging activity and session history.
  </Card>
</CardGroup>

## How to read the reference

If you are building a fleet portal or backend, start with the customer, card, transaction, and understand the available master data endpoints.

If you are building an EV driver app, start with geosearch, session, and remote charging endpoints.

In practice, many products use both parts together: fleet operators need fleet management workflows in the back office, while drivers need charging discovery and charging control in the app.