> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/developer/technical-guides/how-to-guides/mobile/how-to-test-the-inbox-integration.md).

# How to test the Inbox integration?

This guide explains how to verify that your Inbox integration works as expected after implementing a notification center in your app.

The Inbox feature allows you to retrieve and display past push notifications sent to a device or user ID. This feature enables you to create a notification center in your app, where users can find previously received messages.

<figure><img src="https://38998153-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCL8wF0y1T2vLnm3yR2MW%2Fuploads%2FRRVTwjJzfAuSvLTQpJhq%2Finbox.png?alt=media&amp;token=55d7fc4d-3f8e-46d5-80d6-6113bf5bdb08" alt="Mobile app displaying a notification center with recent messages"><figcaption></figcaption></figure>

## Test your integration using a push campaign

To test your Inbox integration, send a standard push campaign from the dashboard. Inbox only stores push notifications sent through campaigns.

To send a test campaign:

{% stepper %}
{% step %}
Open the **Campaigns** tab on the dashboard and click **New Campaign - Push Message**.

<figure><img src="https://38998153-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCL8wF0y1T2vLnm3yR2MW%2Fuploads%2FERjh9o1aHMWn5zNqmtMj%2FNew_Push_Campaign.png?alt=media&amp;token=4d47c957-8ce2-4e44-9897-8b92bd737f6d" alt="Push campaign creation interface on the Batch dashboard"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Create a push campaign that targets the appropriate environment:

* If your app is **not live on the store** or you use a **dedicated test app**, target **All users**.
* If your app is live and no test app is available, create an [**Audience**](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/audiences) with your test devices and target **only this audience**.
  {% endstep %}
  {% endstepper %}

{% hint style="danger" %}
Notifications sent from the **Debug tool** or using the **Send a test** button are not stored in Inbox.
{% endhint %}


---

# 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://doc.batch.com/developer/technical-guides/how-to-guides/mobile/how-to-test-the-inbox-integration.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.