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

# Quick start

> Get your first successful Partner API call

## 1. Get credentials

After Fleeticc enables Partner API on your account (paid add-on — request enablement and pricing via [info@fleeticc.com](mailto:info@fleeticc.com)), the **owner** generates keys in the website dashboard (**Partner API** in the account menu).

| You create | Used for |
| - | - |
| **API key** | Identifies your integration (`X-Api-Key`) |
| **Secret** | Signs every request (keep this private) |

The secret is shown **only once** when you generate or rotate a key. Store it on your server only — never in a mobile app or public website. You can rotate keys anytime from the same page.

## 2. Call the API

Base URL:

```
https://api.fleeticc.com
```

Every request needs three headers (see [Authentication](https://docs.fleeticc.com/api-reference/endpoint/authentication.md)):

* `X-Api-Key`
* `X-Timestamp`
* `X-Signature`

### Request example — list vehicles

```bash theme={null}
export PATH="/usr/bin:/bin:/usr/sbin:/sbin:/opt/homebrew/bin:$PATH"
KEY="$FLEETICC_API_KEY"
SECRET="$FLEETICC_API_SECRET"
REQ_PATH="/api/partner/v1/vehicles"
TS=$(date +%s)
BODY_HASH=$(printf '' | openssl dgst -sha256 -hex | awk '{print $NF}')
SIG=$(printf 'GET\n%s\n%s\n%s' "$REQ_PATH" "$TS" "$BODY_HASH" | openssl dgst -sha256 -hmac "$SECRET" -hex | awk '{print $NF}')

curl -sS -X GET "https://api.fleeticc.com$REQ_PATH" \
  -H "X-Api-Key: $KEY" \
  -H "X-Timestamp: $TS" \
  -H "X-Signature: $SIG"
```

## 3. Typical flow

1. **List vehicles** — save Fleeticc `vehicleId` / `imei` in your system
2. **Live location** — show vehicles on a map
3. **History** — review past trips, or get the location at a specific time

## Available endpoints

| What you need | Method | Path |
| - | - | - |
| Vehicle list | `GET` | `/api/partner/v1/vehicles` |
| Live positions | `GET` | `/api/partner/v1/track` |
| Live updates (stream) | `GET` | `/api/partner/v1/track/stream` |
| History | `GET` | `/api/partner/v1/history` |

## How responses look

**Success**

```json theme={null}
{
  "code": "200",
  "message": "…",
  "data": { }
}
```

**Error**

```json theme={null}
{
  "code": "401",
  "message": "…",
  "data": null,
  "error": "PARTNER_AUTH_INVALID"
}
```

Use the HTTP status and the `error` field when handling failures. Full list: [Error codes](https://docs.fleeticc.com/api-reference/endpoint/error-codes.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.