> 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>" %}