# SCT Tracking Data API
## Context
Once a trip is in progress, we consider the GPS updates as realisation points. The most recent information from your
“tracking device”, as mentioned earlier, should be delivered to our platform as often as possible.
## Example
### Send GPS updates
So, now we are going to send GPS update to the platform. Of course we made sure first that the [tracking device is
already known](/docs/fms/trackingdevice) within the Simacan platform. As the format for this second endpoint is in XML we should stick to the
validation schema.
#### Payload
Make sure that the payload is valid, by looking at the [realisation schema definition](/docs/api/sct-tracking-data/realisation#xml-schema-definition). Your XML should look
like the following snippet:
```xml
1234
2020-06-19T10:11:20.643+00:00
170
84
5.405911
52.192080
```
In this example we use the same externalDeviceId as is known on the Simacan platform. The current timestamp, x/y for
the longitude/latitude, speed in kilometers and heading (where 0 is north).
#### Send it
This example only works, if you obtained a bearer token from our [Auth API](/docs/auth/auth-api).
Include this in the header. Here we post to the production URL
```shell
curl -X POST \
https://sct-tracking-data-api.services.simacan.com/api/v1/realisation \
-H "Authorization: Bearer eyXXX" \
-H "Content-Type: application/xml" \
-d "
1234
2020-06-19T10:11:20.643+00:00
170
84
5.405911
52.192080
"
```
#### Response
Once you receive an HTTP status code 200 OK, then you’ve just made sure that you are ready to send all your updates
to our platform.
*Great! You are totally set to send tracking data updates for specified tracking devices*
## API Marketplace
For a more detailed reference on the SCT Tracking Data API, visit our [API Marketplace](/marketplace)