Runic Developer Platform

The Runic API provides secure access to vehicle tracking, fleet management and telematics data.

Using the API you can:

  • Retrieve the list of vehicles available to your account
  • Get the latest vehicle location and status
  • Access historical tracks
  • Retrieve daily reports
  • Read historical telemetry measurements

Base URL

All API requests should be sent to:

https://api.runic.io/v1

All requests and responses use JSON.


Authentication

The Runic API uses Bearer Token Authentication.

Every request must include an Authorization header:

Authorization: Bearer YOUR_API_TOKEN

Example:

curl \
  --request GET \
  --url https://api.runic.io/v1/vehicles \
  --header "Authorization: Bearer YOUR_API_TOKEN"

Obtaining an API Token

API tokens are currently issued manually. To request access, please contact: [email protected]

Please include:

  • Company name
  • Contact name
  • Email address
  • Intended API usage

Once your request has been reviewed, you'll receive your production API token.

Note

A sandbox environment is not currently available. All API requests are executed against the production environment.


Your First Request

Retrieve the vehicles available to your account.

curl \
  --request GET \
  --url https://api.runic.io/v1/vehicles \
  --header "Authorization: Bearer YOUR_API_TOKEN"

Example response:

{
  "vehicles": [
    {
      "id": 32,
      "name": "Truck 01"
    },
    {
      "id": 41,
      "name": "Delivery Van"
    }
  ]
}

The id returned by this endpoint is used by most other API endpoints.



Response Format

Successful requests return standard HTTP status codes.

StatusDescription
200Request completed successfully
204Request completed successfully with no response body

Errors are returned using standard HTTP status codes.

StatusDescription
400Invalid request
401Authentication failed
403Access denied
404Resource not found
429Rate limit exceeded
500Internal server error

Refer to the Errors section for more details.


Rate Limits

To ensure a reliable service for all customers, the API is protected by rate limiting.

If you exceed the allowed request rate, the API will return:

HTTP/1.1 429 Too Many Requests

The response may also include a Retry-After header indicating when you should retry the request.

We recommend implementing exponential backoff when retrying failed requests.


Need Help?

If you have any questions about the API or need access credentials, contact: [email protected]







Did this page help you?