Getting started
Sign in with POST /auth, then make your first vehicle request.
1. Sign in
Send your KATSANA account email as username, together with your password:
curl --request POST https://api.katsana.com/auth \
-H 'Accept: application/vnd.KATSANA.v1+json' \
-H 'Time-Zone: Asia/Kuala_Lumpur' \
-H 'Content-Type: application/json' \
--data '{"username":"<your-email>","password":"<your-password>"}'
The response contains a token field. Copy its value into your terminal environment:
export KATSANA_TOKEN='<token-from-auth-response>'
Keep your password and token private. See authentication for token handling and browser request availability.
2. List your vehicles
Use the token in the Authorization header:
curl https://api.katsana.com/vehicles \
-H 'Accept: application/vnd.KATSANA.v1+json' \
-H 'Time-Zone: Asia/Kuala_Lumpur' \
-H "Authorization: Bearer $KATSANA_TOKEN"
The response contains your accessible vehicles in devices. V1 is selected through the Accept header; there is no /v1 prefix in the URL.
3. Get a vehicle’s location
Replace <vehicle-id> with an ID from the vehicle list:
curl 'https://api.katsana.com/vehicles/<vehicle-id>/location' \
-H 'Accept: application/vnd.KATSANA.v1+json' \
-H 'Time-Zone: Asia/Kuala_Lumpur' \
-H "Authorization: Bearer $KATSANA_TOKEN"
The response contains the latest tracker position. Location availability and freshness depend on the device.
Continue in the API reference
Test Request prefills the editable request fields with the documented examples, including the JSON username and password body for sign-in and the Asia/Kuala_Lumpur timezone header. Edit the values directly before sending. A successful sign-in fills the API token field for subsequent requests. A vehicle or fleet ID entered in a path field is reused in later matching requests; a successful list also supplies an ID when you have not entered one. Each request keeps your own edits. Sign-in clears the previous resource IDs, and reloading clears the session.
Next steps
- API reference — explore operations and response fields.
- Pagination and timezones — work with larger fleets and historical data.
- Errors — handle unsuccessful requests.
- Downloads — get OpenAPI and Postman files.