The Skrym standardized tracking system will help you know what is going on with your shipments. Use it to keep track of every package that you send, inbound as well as outbound - regardless of transporter or transport method. You also get access to automated statistics that can help you evaluate how well your transporters are living up to their promises. 1. Get your API credentials and Scope login from your Skrym contact. To learn more, have a look at the page. 2. You can now make a call to ! 3. Go to or call to verify your shipment is being tracked. ## Transporter authentication For some transporters, you need to complete some additional steps in order for Skrym to have access to the events. In the table below, you can see if any particular steps are required for your transporters. | Transporter | Steps | | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | No steps required. | | | You need to add Skrym to the list of destinations for the event subscriptions by following the steps in the .
The URL you specify should be `https://api.skrym.com/tracking.BudbeeTrackingWebhook` and you need to add a HTTP Basic authentication with a username and password that Skrym can provide you with. | | | _Coming soon_ | | | _Coming soon_ | | | _Coming soon_ | --- ## Add a shipment to track Shipments are added to tracking by calling **core.InitializeTracking** endpoint with the transporter and transport method information and the concerned tracking reference. Once this endpoint has been successfully called, Skrym will be fetching and parsing the event data made available by the transporter and provide it to you immediately. --- ## Fetching shipment information ### Single shipment 📦 Now try fetching tracking information for that shipment using the tracking API. As the response body is quite exhaustive, we recommend you to reach out if you have any questions regarding a particular field. ### Multiple shipments 📦📦📦 It is also possible to fetch information regarding all your shipments and provide a filter. --- ## Subscribe to your events We want to enable you to take action as soon as there is something wrong with a shipment rather than having to wait for the customer to complain. That's why Skrym comes with native support for adding your own webhook subscriptions. A webhook is a way to "automate" the communication between systems by adding "suscriptions" to events (e.g. an update or insert happening to a data object). If you want to learn more, we recommend checking out this{' '} To set up a webhook, navigate to the tab on Scope under TMS. On this page, you can add new webhooks (incl. authentication tokens) that Skrym will send the tracking events to. At the moment, Skrym does not support HTTP Basic Authentication. {/* ADD DEMO AND SCREENSHOTS HERE */} There's a ton of different use cases that can be interesting to explore with this technology. To get a better understanding of what each event means, you can have a closer look at the in-depth section explaining our data structure for shipping events:

Shipping