Quickstart

Authenticate, query your fleet, and explore the API — all in under 5 minutes.

Prerequisites

• API credentials: email, password, and apiKey provided during onboarding

Step 1 — Authenticate

Obtain a JWT token by calling the login endpoint:

cURL

curl -s -X POST \
  -H "tenant: $TENANT" \
  -H "Content-Type: application/json" \
  -d '{"email":"dev@yourcompany.com","password":"your_password"}' \
  "https://$TENANT/apidev/v1/login"

JavaScript

const TENANT = 'geotareas.com';
const API_KEY = 'gtk_prod_xxxxxxxxxxxx'; // from onboarding

const loginRes = await fetch(`https://${TENANT}/apidev/v1/login`, {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'tenant': TENANT,
  },
  body: JSON.stringify({
    email: 'dev@yourcompany.com',
    password: 'your_password',
  }),
});

const { data } = await loginRes.json();
const token = data.authorization;

Python

import requests

TENANT = "geotareas.com"
API_KEY = "gtk_prod_xxxxxxxxxxxx"  # from onboarding

login = requests.post(
    f"https://{TENANT}/apidev/v1/login",
    headers={"tenant": TENANT, "Content-Type": "application/json"},
    json={"email": "dev@yourcompany.com", "password": "your_password"},
)

token = login.json()["data"]["authorization"]

PHP

$tenant = 'geotareas.com';
$apiKey = 'gtk_prod_xxxxxxxxxxxx'; // from onboarding

$ch = curl_init("https://{$tenant}/apidev/v1/login");
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_HTTPHEADER => ["tenant: {$tenant}", "Content-Type: application/json"],
    CURLOPT_POSTFIELDS => json_encode(['email' => 'dev@yourcompany.com', 'password' => 'your_password']),
    CURLOPT_RETURNTRANSFER => true,
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);

$token = $response['data']['authorization'];

C#

using System.Net.Http;
using System.Text;
using System.Text.Json;

var tenant = "geotareas.com";
var apiKey = "gtk_prod_xxxxxxxxxxxx"; // from onboarding

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("tenant", tenant);

var payload = JsonSerializer.Serialize(new {
    email = "dev@yourcompany.com",
    password = "your_password"
});

var loginResponse = await client.PostAsync(
    $"https://{tenant}/apidev/v1/login",
    new StringContent(payload, Encoding.UTF8, "application/json"));

var loginJson = JsonDocument.Parse(await loginResponse.Content.ReadAsStringAsync());
var token = loginJson.RootElement.GetProperty("data").GetProperty("authorization").GetString();

Response:

{
  "success": true,
  "data": { "authorization": "eyJhbGciOi..." },
  "meta": {}
}

tip

The token is valid for 1 hour. There is no refresh endpoint — simply re-authenticate when it expires. The API Key (gtk_prod_...) is permanent and was provided during onboarding — you'll use it alongside the token in every request from here on.

Step 2 — Query your fleet

Use the token + API key to call any protected endpoint. Every request requires 3 headers:

Authorization: Bearer <token>
X-API-Key: <your_api_key>
tenant: <your_tenant>

cURL

curl -s \
  -H "Authorization: Bearer $TOKEN" \
  -H "X-API-Key: $APIKEY" \
  -H "tenant: $TENANT" \
  "https://$TENANT/apidev/v1/fleet/devices?limit=5&status=A"

JavaScript

const headers = {
  'Authorization': `Bearer ${token}`,
  'X-API-Key': API_KEY,
  'tenant': TENANT,
};

const res = await fetch(
  `https://${TENANT}/apidev/v1/fleet/devices?limit=5&status=A`,
  { headers }
);
const devices = await res.json();
console.log(devices.data);

Python

headers = {
    "Authorization": f"Bearer {token}",
    "X-API-Key": API_KEY,
    "tenant": TENANT,
}

devices = requests.get(
    f"https://{TENANT}/apidev/v1/fleet/devices",
    headers=headers,
    params={"limit": 5, "status": "A"},
)
print(devices.json()["data"])

PHP

$ch = curl_init("https://{$tenant}/apidev/v1/fleet/devices?limit=5&status=A");
curl_setopt_array($ch, [
    CURLOPT_HTTPHEADER => [
        "Authorization: Bearer {$token}",
        "X-API-Key: {$apiKey}",
        "tenant: {$tenant}",
    ],
    CURLOPT_RETURNTRANSFER => true,
]);
$devices = json_decode(curl_exec($ch), true);
curl_close($ch);

print_r($devices['data']);

C#

client.DefaultRequestHeaders.Clear();
client.DefaultRequestHeaders.Add("Authorization", $"Bearer {token}");
client.DefaultRequestHeaders.Add("X-API-Key", apiKey);
client.DefaultRequestHeaders.Add("tenant", tenant);

var devicesResponse = await client.GetStringAsync(
    $"https://{tenant}/apidev/v1/fleet/devices?limit=5&status=A");
var devices = JsonDocument.Parse(devicesResponse);

Response:

{
  "success": true,
  "data": [
    {
      "id": "104820579301",
      "name": "Truck-42",
      "plate": "ABC-1234",
      "status": "A",
      "lastPosition": {
        "lat": -34.6037,
        "lng": -58.3816,
        "speed": 45,
        "timestamp": "2026-04-04T14:23:00"
      }
    }
  ],
  "meta": { "total": 128, "limit": 5, "offset": 0 }
}

Step 3 — Explore the full API

You've authenticated, read data, and performed a write operation. Here's what else you can do:

Domain	Try this	Endpoint
Fleet	List vehicles with GPS position	GET /fleet/devices
Fleet	List drivers and assignments	GET /fleet/drivers
Telemetry	Ingest GPS points from devices	POST /telemetry
Tasks	Create and update tasks	POST /tasks
Tasks	Download task attachments	GET /tasks/{id}/attachments
Catalogs	Origins, products, coverages	GET /catalogs/origins
Geocoding	Resolve an address to coordinates	POST /geocoding/forward
Reports	Kilometers traveled in a date range	GET /reports/avl/kilometers
Reports	Task detail with dynamic fields	GET /reports/gt/tasks-general
Reports	Live location of the field crew	GET /reports/gt/live-location

All paths are prefixed with /apidev/v1/.

Testing with Postman

A ready-to-use Postman collection is available. See the Postman Collection page for import instructions and the full list of pre-built requests.

What's next

By use case:

• Fleet tracking & IoT — Fleet & Telemetry, AVL Reports
• Task management — Tasks, Task Attachments
• Field operations — GT Operations Reports, Live Location
• Addresses & coverage — Geocoding, Catalogs

Fundamentals:

• Authentication — Full dual-auth model and troubleshooting
• Rate Limits — Understand limits and avoid 429 errors
• Error Handling — Standard error envelope and codes
• API Coverage — Complete endpoint inventory (90+ endpoints)