> 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/engage/messages-and-journeys/overview/push-notifications.md).

# Push Notifications

Send push notifications that provide order status updates within your app and website to proactively communicate with your customers.

## Overview

You can set up order status updates through push notifications for your application or website (desktop and mobile versions).

{% hint style="info" %}
parcelLab support integrations that serve push notifications in your preferred channel. For more information on the scope and requirements of this feature, please contact your parcelLab representative.
{% endhint %}

## Configuring Push Notifications

The following sections describe the configuration required for push notifications.

For each push notification to be sent, we define a trigger as for email communications sent from parcelLab. That information is pushed via webhook to your own push notification service or directly to your application.

A direct integration with your app is possible via API. Refer to the [documentation on app integration](https://github.com/parcelLab/gitbook-documentation/tree/main/developers/status-updates/apps.md) for further information.

### Customer Requirements

For setting up push notifications using webhooks, you need to provide the following information:

* Your webhook URL.
* The triggers to be used, which perform an action based on events (for example: the pickup ready notification is triggered when a delivery is ready to be collected at a parcel shop or parcel locker, and also on delivery to a neighbor).
* Push notification service credentials (that is: tokens and keys).
* The necessary payload, which usually includes the type of notification to be triggered and order-related data.

{% hint style="info" %}
For further details, please contact your parcelLab representative.
{% endhint %}

### Implementation Process

In this section, the next steps in the setup process are described.

There are two ways to define the content of push notifications:

1. The content is directly defined in our messages, which can be localized.
2. The content is managed in your APNS and identified by a message ID that is sent from parcelLab.


---

# 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/engage/messages-and-journeys/overview/push-notifications.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.