Dealer and Support API
These endpoints cover dealer workflows, license management, and support ticketing.
Dealer operations
- Name
GET /api/dealers/:id- Description
Get one dealer with its licenses. For
account_type: DEALERthe:idis ignored and your own dealer record is returned.
- Name
GET /api/dealer/:dealerId/audit-logs- Description
Audit log entries for the calling user.
- Name
GET /api/licenses/:id- Description
- Get license details.
- Name
PUT /api/licenses/:id- Description
- Update license details.
Dealer lookup parameters
- Name
page- Type
- integer
- Description
- Default
1.
- Name
limit- Type
- integer
- Description
- Default
100.
- Name
expiring_in_days- Type
- integer
- Description
Only include licenses expiring within this many days.
- Name
query- Type
- string
- Description
Search license ID, vehicle number, or IMEI.
For a DEALER account you can pass your own dealer ID, or any value — the server
resolves the record from your credentials.
Dealer with licenses
curl -G "$LIVEPIN_API_BASE_URL/api/dealers/9" \
-H "Authorization: Bearer $JWT_TOKEN" \
-H "x-api-key: $LIVEPIN_API_KEY" \
-d limit=50 \
-d page=1 \
-d expiring_in_days=30
Dealer audit logs
curl "$LIVEPIN_API_BASE_URL/api/dealer/9/audit-logs" \
-H "Authorization: Bearer $JWT_TOKEN" \
-H "x-api-key: $LIVEPIN_API_KEY" \
-d page=1 \
-d limit=100
The :dealerId path parameter is not used by this endpoint. Audit logs are always
returned for the calling user, so pass your own dealer ID for clarity. The
page and limit parameters are supported; limit defaults to 100.
License details
curl "$LIVEPIN_API_BASE_URL/api/licenses/:licenseId" \
-H "Authorization: Bearer $JWT_TOKEN" \
-H "x-api-key: $LIVEPIN_API_KEY"
Support operations
- Name
POST /api/support-tickets- Description
- Create support ticket.
- Name
PUT /api/support-tickets/:id- Description
Update support ticket.
- Name
GET /api/support-tickets- Description
List support tickets with status filters.
- Name
DELETE /api/support-tickets/:id- Description
Delete support ticket.
Create support ticket
curl -X POST "$LIVEPIN_API_BASE_URL/api/support-tickets" \
-H "Authorization: Bearer $JWT_TOKEN" \
-H "x-api-key: $LIVEPIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"subject":"Device not reporting","description":"IMEI 377079642594 stopped sending data"}'
Update support ticket
curl -X PUT "$LIVEPIN_API_BASE_URL/api/support-tickets/:ticketId" \
-H "Authorization: Bearer $JWT_TOKEN" \
-H "x-api-key: $LIVEPIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"status":"resolved"}'
Restrict these routes with role-based access control and server-to-server authentication only.
