Getting Started

This guide helps you integrate quickly with the Jitra Public API and avoid common setup issues.

Overview

The Public API provides read access to organization data such as objects, positions, geofences, routes, and sites.

Prepare the following:

Use the public base URL:

https://api.jitra.app/public/v1

Append resource paths to that base URL.

All endpoints require an API key.

You can authenticate with either header:

If the key is missing, invalid, or expired, the API returns 401.

Recommended header examples:

x-api-key: <api_key>

Authorization: Bearer <api_key>

Requests are rate-limited per organization.

Setting	Value
Window	10 seconds
Max requests	10 requests per window

When the limit is exceeded, the API returns 429.

Successful responses use:

{
  "statusCode": 200,
  "result": {}
}

result can be an object or an array depending on the endpoint.

Error responses follow:

{
  "statusCode": 400,
  "errorCode": "PUBLIC.400_001",
  "message": "Validation error message",
  "timestamp": "2026-05-17T01:00:00.000Z"
}

Use this sequence to validate integration in minutes:

This is the safest first call because it requires no path or query parameters.

curl --request GET \
  --url https://api.jitra.app/public/v1/objects \
  --header 'x-api-key: <api_key>'

Take one id from step 1:

curl --request GET \
  --url https://api.jitra.app/public/v1/objects/101 \
  --header 'x-api-key: <api_key>'

Request multiple IDs in one call:

curl --request GET \
  --url 'https://api.jitra.app/public/v1/positions/latest?ids=101,102' \
  --header 'x-api-key: <api_key>'

HTTP Status	Meaning	Typical Action
200	Request succeeded	Process `result`.
400	Invalid request input	Fix path/query values and retry.
401	Authentication failed	Check API key value and header format.
404	Resource not found	Confirm the requested object exists in your organization.
429	Rate limit exceeded	Retry with backoff after waiting for the next window.