The PowUnity tracking server includes a web API to access GPS tracking data from your trackers using a REST API. Documentation for the API can be found in our API Reference which is based on the Swagger format.
...
Using session cookies (see "session" URL path)
Standard HTTP authorization header
View API documentation:
Access token
As an alternative to email and password login, there is an option to use an account token for authorisation.
...
To create a token use the "token" query parameter in a session GET request:
Code Block |
---|
https://traccariot.powunity.com/api/session?token=YOUR_ACCESS_TOKEN |
...
In addition to the REST API, we provide access to a WebSocket endpoint for live location updates and events. The URL for the connection:
Code Block |
---|
wss://traccariot.powunity.com/api/socket |
Session cookie is the only authorization option for the WebSocket connection.
...
Log in to https://traccar.powunity.com
click
Settings
at the top right:Select
Account
Click on the
Attributes
button in the dialog that openedUse the
+
button to add the following attributes to the table - NOTE: Attribute names are case sensitive!webhookUrl
This is the URL that will be called on every new event via a HTTP POST request. We highly encourage to use a URL starting with https:// but http:// is also supported for testing purposes.webhookPsk
Optional. If set, the HTTP(S) requests will contain a Authorization header with this attribute’s data as value. This should allow Basic and Bearer authorization methods to be implemented easily.webhookTypes
Optional. If set, this should be a comma (,) separated list of event types which are to be forwarded by the webhook. If this attribute is not present then all events are sent. Some useful possible values are:deviceOnline
,deviceOffline
,deviceMoving
,deviceStopped
,alarm
,geofenceEnter
,geofenceExit
,ignitionOn
,ignitionOff
Here is what the Attributes dialog could look like:
Once the attributes are set close the Attributes and Account dialogs. The webhooks are then activated immediately.
Info |
---|
Non-alert events are ignored for non-b2b users or in case disableWebhooks is "true" |