> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/developers/data-elements/get-status-updates.md).

# Get Status Updates

Provide the latest status of their orders to your customers via our powerful integration options.

## Overview

Retrieving a tracking from parcelLab refers to the act of requesting the information about a certain delivery. The progress and tracking updates returned are known as checkpoints.

When you have this data, you can keep your customers updated on the progress of their orders via a variety of sources.

## Status Update Integration Methods

You can use our API to retrieve checkpoint and tracking data from parcelLab to feed back into your e-commerce system. This flexible method allows you to submit all the necessary order and tracking information and receive the relevant status details instantly.

{% content-ref url="/pages/DugFoG9SGRM7zZdaaWxH" %}
[Order Status](/docs/developers/status-updates/order-status.md)
{% endcontent-ref %}

You can also use our API to retrieve the current status of an order or parcel for use with the following:

* Any [customer facing widget](https://github.com/parcelLab/gitbook-documentation/tree/main/developers/status-updates/chatbots/README.md), such as chatbots
* Any [native or web app](https://github.com/parcelLab/gitbook-documentation/tree/main/developers/status-updates/apps.md)

## Configure Tracking Webhooks

API v4 customers can configure tracking-status webhooks in the parcelLab App when Messages, Journeys, and the required integration are available to their user. The API version used to send order data does not subscribe the account to outbound events.

1. Add a webhook integration with your receiver URL and authentication settings in the [integration settings](https://app.parcellab.com/service/config/integration/). You can add an integration there, but you cannot edit or delete it; ask parcelLab to change an existing integration.
2. In **Experience Design > Messages**, create a message type with the **Webhook** channel and add the payload content.
3. In **Journeys**, add a trigger for the required tracking event. Set its filters, select the webhook message type, and select the destination integration.
4. Publish the message and journey changes. Publishing requires the **Experience Design Admin** role, which only parcelLab can grant. With the **Experience Design Manager** role, you can save changes; ask your parcelLab representative to publish them. Test with a matching tracking, then check the request and response in **Communication > Webhooks**.

The Webhooks list contains delivery records; it is not the subscription editor. If you cannot access these settings, or your account uses a setup managed by parcelLab, ask your parcelLab representative to configure the integration and triggers. Provide the receiver URL, required events, payload fields, and authentication requirements.

The [tracking webhook reference](https://github.com/parcelLab/gitbook-documentation/tree/main/developers/data-elements/get-status-updates/webhooks.md) describes standard tracking events and their payload. For a custom Journey webhook, use the payload defined in its message.

For return-registration exports, see [Receive Order Data](/docs/developers/returns/receive-order-data.md#configure-return-webhooks).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parcellab.com/docs/developers/data-elements/get-status-updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.