> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/crm-v1-old/campaigns/how-to-use-api-campaigns-to-track-status-of-messages-sent-via-api-delivered-read-failed.md).

# How To Use API Campaigns To Track Status Of Messages Sent Via API ( Delivered / Read / Failed ) ?

#### Overview of API Campaigns

API campaigns offer a streamlined way to track messages sent by a specific access token. This feature enables users to monitor messages associated with a certain API key or token.

#### Creating an API Campaign

1. **Select Channel**: Choose the appropriate channel for your campaign.
2. **Enter Campaign Name**: Name your campaign for easy identification.
3. **Token Validity**: Decide if the token is lifetime or has a limited validity period.

Upon creation, a token is generated. Copy and paste this token as the bearer token in your authorization to use the API campaign feature.

#### Sending Messages via API

The procedure for sending messages via API remains unchanged. However, use a different token per campaign to ensure proper tracking.

#### Monitoring Reports

In the reports section, users can track message statuses such as delivered, read, or failed. Reports can be exported as CSV files, providing detailed data and statistics.

#### Notes

* The structure of the API call for sending messages remains consistent.
* The token and authorization token will vary for each campaign, allowing users to track API-sent messages effectively.

{% embed url="<https://youtu.be/ZAmd8kxRRD4?si=h465CRTWxvRcwzW7>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdocumentation.gitbook.io/user/crm-v1-old/campaigns/how-to-use-api-campaigns-to-track-status-of-messages-sent-via-api-delivered-read-failed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.