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

# REST API introduction

> Introduction to the c.technology vehicle REST API

## Welcome to the c.technology REST API

The c.technology vehicle REST API provides the ability to programmatically manage and interact with the full range of c.technology products and services.
This includes managing vehicles, trips, notifications, maintenance schedules, and much more.

<Note>
  Please reach out to us for access to OEM-specific fields and endpoints.
  This documentation focuses on the general-purpose API used by self-service and standard customers.
</Note>

## Key features

* **Vehicle management**: Get and update vehicle profiles, monitor status, and retrieve action logs
* **Trip tracking**: Access trip data, triplegs, and manage trip records
* **Authentication**: Token-based authentication with personal or programmatic access tokens
* **Comprehensive data**: Access to notifications, maintenance, insights, and more
* **Real-time updates**: Many endpoints have real-time counterparts via the [AsyncAPI](/asyncapi-reference/introduction)

## API Version

The c.technology API is versioned with the version identifier as part of the URL:

```
https://api.ctechnology.io/api/v2.2/...
```

The current version is `v2.2.0`. You can use `v2.2` without the patch version, as the API is backwards-compatible between patch versions.

## Authentication

Most endpoints require authentication using access tokens. Include your token in the HTTP `Authorization` header:

```
Authorization: Token {your_token}
```

You can obtain a personal access token via the login endpoint, or create a programmatic access token from your admin panel.

## Request & Response Format

Standard communication is done using JSON with an `application/json` content type. Responses always are of the following structure:

```json theme={null}
{
  "header": {
    "api_version": "v2.2",
    "status": "SUCCESS",
    "message": "...",  // Important for errors    
    ...
  },
  "data": { ... }
}
```

Datetime fields use ISO 8601 format in UTC: `YYYY-MM-DDThh:mm:ss.sssZ`

## Rate Limiting

Rate limiting is in place and depend on individual endpoints.
If you receive a `429 Too Many Requests` response, check the `Retry-After` header for when you can retry your request.
For push-based data updates without rate limits, consider using the [AsyncAPI](/asyncapi-reference/introduction) or webhooks.