Connect Jitra tracking data to the systems you already use.
Read supported Organization resources through the Jitra Public API or send Event occurrences to an external HTTPS endpoint with webhooks. Start with the integration capacity included in Jitra Pro.
Pull tracking data or react when an Event occurs.
Public API
Read supported Objects, positions, Places, and route resources from the authenticated Organization.
Event Webhooks
Send a versioned payload to an approved external endpoint after a supported Event rule is triggered.
Email Delivery
Send supported Event notifications to configured recipients under the active Integration entitlement.
Read the tracking resources your application needs.
Jitra Public API currently provides read-only access to supported Organization data through versioned HTTPS endpoints.
- Objects.
- One Object with available location, telemetry, and metadata.
- Historical positions for one Object within a required range.
- Latest positions for requested Object IDs.
- Polygon geofences.
- Circular sites.
- Routes and ordered route points.
Authentication: Organization API key using x-api-key or Bearer authentication.
From API key to tracking data.
- 01
Define the use case
Decide which Organization resources your client needs.
- 02
Create an API key
Create a named credential and use a short duration for initial testing.
- 03
Call the versioned endpoint
Authenticate over HTTPS and request a supported resource.
- 04
Handle limits and errors
Implement 429 backoff and parse consistent response wrappers.
- 05
Monitor usage
Review Integration usage against the active entitlement.
Send supported Events to an external workflow.
When a configured Event rule is triggered, Jitra can create an Event occurrence and deliver a versioned payload to an approved HTTPS endpoint. Webhook delivery is independent from the in-app notification inbox.
- Event-based trigger.
- HTTPS POST delivery.
- Versioned payload.
- Optional secret and signature where configured.
- Payload example and test delivery in the supported workflow.
- Delivery status is recorded without removing the Event occurrence when delivery fails.
Current setup note: The current UI can enable webhook delivery on an Event, but destination provisioning is not fully self-serve. Coordinate the endpoint setup with your Organization administrator or Jitra support.
Bring tracking data into the systems your team already uses.
Operations dashboard
Read current Object and latest-position data for an internal view.
Movement history review
Request historical positions for an approved Object and time range.
Location-aware workflow
Use supported geofence, site, or route resources as context in another system.
Event automation
Let an external system react when a supported geofence, movement, speed, GPS signal, or sensor Event occurs.
Start with Pro, then increase capacity when needed.
External API, Webhook, and Email channels are not available on Free. Every Pro Organization receives Integration Free with starter capacity per Object and per day. Integration+ increases channel quotas for higher-volume use.
Keep credentials and customer data under control.
- Store API keys in secure secret storage, never in public source code.
- Use HTTPS in every environment.
- Scope access to the correct Organization.
- Do not expose keys, webhook secrets, or customer payloads in screenshots or support messages.
- Public API access remains limited to documented resources and methods.
Frequently asked questions.
No. The current Public API is read-only and only exposes documented resources and methods.
Evaluate the integration with real Jitra data.
Create an account, connect an Object, then use Jitra Pro when you are ready to issue an API key or configure an external delivery channel.