> 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/backend/how-to-connect-batch-to-my-cms.md).
# How to connect Batch to my CMS?
Connecting Batch to a CMS to send push notifications is straightforward. You can use our Campaigns API.
You can connect your CMS to Batch to send push notifications using the [Campaigns API](/developer/api/cep/campaigns.md). It gives you the same level of features as the Batch dashboard:
* **Targeting**: Basic, native and custom attributes targeting
* **Scheduling**: Scheduled and recurring push automations
* **Messaging**: A/B testing, deeplink, custom payload, rich push notifications, etc.
Here is what a basic **Campaigns API + CMS** setup looks like:
With the Batch APIs, you can:
* [**Create**](https://doc.batch.com/developer/api/cep/campaigns/create)**,** [**update**](https://doc.batch.com/developer/api/cep/campaigns/update)**, or** [**delete**](https://doc.batch.com/developer/api/cep/campaigns/delete) an existing push campaign. If the POST to the API endpoint is successful, you will receive an HTTP 201 confirmation with an orchestration ID. Each time you send a push notification, Batch receives feedback from APNS/FCM and cleans the invalid tokens for you.
* **Get reports on your campaigns:**
* Use the Batch Orchestrations API to [list orchestrations](/developer/api/cep/orchestrations/list.md) and [get orchestrations stats](/developer/api/cep/orchestrations/stats.md)
* Use the Batch Export API to [generate granular Events exports](/developer/api/cep/profiles/export.md).
---
# 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/backend/how-to-connect-batch-to-my-cms.md?ask=&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.
