### API Base Path and Version

Source: https://flespi.io/docs

Information about the base path and version of the Flespi Telematics Hub REST API.

```APIDOC
## API Base Path and Version

### Base Path
`/gw`

### Version
`1.0`
```

--------------------------------

### Resource Management

Source: https://flespi.io/docs

Overview of the main resources available in the Flespi Telematics Hub API.

```APIDOC
## Resource Management

### Description
The Flespi Telematics Hub API allows management of various telematics-related resources.

### Resources
- **channels**: Inbound protocol-specific pipes for data parsing and storage.
- **devices**: Virtual representations of physical trackers for message storage, configuration, and telemetry.
- **streams**: Outbound data flows for forwarding telematics data to target platforms.
- **calculators**: Rules for interval detection and value computation for analytics.
- **plugins**: Extend standard device parameters and functionality.
- **modems**: Interface for sending configuration messages via SMS.
- **protocols**: Access to protocol lists, device types, message parameters, and commands.
```

--------------------------------

### General API Information

Source: https://flespi.io/docs

General information and constraints for the Flespi Telematics Hub REST API.

```APIDOC
## General API Information

### URI Component Limit
The limit for any URI component is 64KB.

### Logging
All changes to gateway items are recorded in the common logs subsystem.
```

--------------------------------

### Authentication

Source: https://flespi.io/docs

All REST requests to the Flespi API require an authentication token to be passed in the HTTP header.

```APIDOC
## Authentication

### Description
To authenticate REST requests, include your Flespi token in the `Authorization` header.

### Header
`Authorization: FlespiToken XXXXXXXXXX`
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.