> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/integration/data-api/api-overview/before-you-start.md).
# Before you start
Before you can start requesting ads, you will need sandbox access, your team ID and API key, and active campaigns.
## Sandbox access
To integrate with Epsilon Retail Media, you will need a sandbox created on your behalf. Your Technical Account Manager will work with you on this, and provide you with access once it is created.
Should you not have access, contact your Technical Account Manager, or contact our support team.
## Your team ID and API key
To sync products and interact with our API, you will need your retailer team's ID, and your API key. Once logged into your retailer team, click the dropdown menu in the top right and click **Integration Settings**
Your team ID is displayed here, which is the Team ID to use where required in API calls. This value will change depending on whether you are in your sandbox or production environment.
Click the API Key option in the secondary menu - you will see your secret API key is hidden.
To retrieve your secret API key, click the 'show' button, and copy it. This is the API key to use in API calls. This value will change depending on whether you are in your sandbox or production environment.
## Active campaigns
For Epsilon Retail Media to return ads, active and approved campaigns need to be created in your sandbox. You will need to synchronise your catalog with at least one product prior to creating campaigns.
---
# 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://help.citrusad.com/retail-media-interface/integration/data-api/api-overview/before-you-start.md?ask=&goal=
```
`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.