> For the complete documentation index, see [llms.txt](https://docs.parameter1.com/base-cms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parameter1.com/base-cms/newsletter-management/new-framework/campaign-deployment/using-base-for-esp-integration/initial-omeda-requirements.md).

# Initial Omeda Requirements

Base doesn’t deploy newsletters on its own - it uses *Omeda’s* API to deploy the newsletters.  Think of it like another interface to deploy the newsletters from, where *Omeda* is still the one doing the sending, but Base is the one that's sending *Omeda* the necessary information to get it done.

In order to setup the integration, you'll need to gather the following data from *Omeda:*

## Global *Omeda* Account info:

* **API Key:**`XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX`
* **Client Key:** `client_abc`
* **Brand Abbreviation Key:**`abc`
* **Input ID:** `XXXXXXXXXXXXXXX`
* **\_identified ID:** `123`
* **\_registered ID:**`124`
* **Omail Developer Account:** We'll need a separate developer account setup that Base will use to communicate with Omail as the "sender".  Please send the username and password to your site administrator during initial setup.

### Individual Newsletter Info:

Alongside the global *Omeda* account info, each newsletter that is to be deployed through Base will need the following info:

* **Deployment Type ID** (not to be confused with the Product ID)
* **OnQ Query Name** (Also known as the “Audience List” name or “Mailing List” name )

Optional addition per newsletter, but not required:

* **BillingCategoryCode** (8 characters long, will likely be the same for all newsletters)