> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/blotout-cloud/configuration.md).

# Configuration

Now that the basic onboarding is complete, let's review all fields in the form and how to use them. The App Token, App Name, and Collection Endpoint URL were already filled in during the basic onboarding, so we will skip those three.

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FRZL0da0ZZ9ud5vQ2wF6b%2Fimage.png?alt=media&amp;token=0dad35c0-0a3d-49ff-96ed-a004a0df379d" alt=""><figcaption></figcaption></figure>

### Blotout Version

The **Blotout Version** field allows you to specify which version of the Blotout Cloud API to use for event processing. This field ensures compatibility between EdgeTag and your Blotout Cloud instance, allowing you to control API versioning based on your deployment requirements.

Different versions may support different features or event formats, so selecting the correct version ensures optimal performance and feature availability. If you're unsure which version to use, consult with your Blotout team or refer to your cloud deployment documentation.


---

# 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.edgetag.io/channels/blotout-cloud/configuration.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.