> ## Documentation Index
> Fetch the complete documentation index at: https://developers.everflow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Marketplace API

> Reference documentation for the Marketplace API

The Marketplace API is only relevant for users who have an account on [partners.everflow.io](https://partners.everflow.io/) and connections on the Marketplace. If you are looking for the affiliate API documentation, please refer to the [Affiliate API](/api-reference/affiliate-overview) instead.

## Everflow's Marketplace API model

Partners who participate in the Marketplace on Everflow establish connections with one or multiple brands. Data fetched from the Marketplace API will include relevant information from all the brands with which a connection was established.

For example, when fetching offers from the Marketplace API while being connected to 3 different brands you can expect the following:

<Frame caption="Top level model of the Everflow Marketplace API">
  <img src="https://storage.googleapis.com/everflow-documentation/api/marketplace/marketplace-api-top-level.png" />
</Frame>

Everflow, however, is a software provider and does not act like a network. Consequently, each brand actually "owns" their own instance of Everflow from which data is exposed through the [Affiliate API](/api-reference/affiliate-overview).

When Marketplace partners create a connection with a brand in Everflow, they also gain access to the brand's affiliate API which exposes all the data available in the Everflow UI.

The Marketplace API serves as an umbrella over the different brand connections and allows API users to fetch data from all brands in a single call.

<Frame caption="Inner workings of the Everflow Marketplace API">
  <img src="https://storage.googleapis.com/everflow-documentation/api/marketplace/marketplace-api-affiliate-apis.png" />
</Frame>

In other words, using the Marketplace API is actually optional, since API users are free to access the [Affiliate API](/api-reference/affiliate-overview) directly:

<Frame caption="Direct connection with a brand's Affiliate API">
  <img src="https://storage.googleapis.com/everflow-documentation/api/marketplace/affiliate-api-connection.drawio.png" />
</Frame>

And since there is no aggregation layer between the Affiliate API and the API user, there are scenarios in which it can be beneficial to access the [Affiliate API](/api-reference/affiliate-overview) directly. For example, more filters will be offered on reporting and offer endpoints.

### Power users

Because Everflow works with a one-instance-per-brand model, power users of the API should explore this way of working, which essentially involves 2 steps:

1. Fetch the API key associated with each brand the partner is connected with through [this endpoint](/api-reference/get-partnersconnectionsapikeyslist).
2. Use the [Affiliate API](/api-reference/affiliate-overview) to accomplish the required task.

<Frame caption="Direct connection with a brand's Affiliate API">
  <img src="https://storage.googleapis.com/everflow-documentation/api/marketplace/api-keys-then-affiliate-calls.png" />
</Frame>

## API keys

API keys for the Marketplace API are found in the **API** tab of the **My Account** section on [partners.everflow.io](https://partners.everflow.io/). All Marketplace API endpoints use the `X-Eflow-Api-Key` header for authentication.

<CardGroup cols={2}>
  <Card title="API Keys" icon="key" href="/api-reference/get-partnersconnectionsapikeyslist">
    Operations for affiliate API keys.
  </Card>

  <Card title="Connections" icon="link" href="/api-reference/post-partnersconnectionstable">
    Operations to fetch connections with brands.
  </Card>

  <Card title="Earnings" icon="dollar-sign" href="/api-reference/post-partnerspayments">
    Operations for Earnings / Payments.
  </Card>

  <Card title="Marketplace Advertisers" icon="building" href="/api-reference/post-partnersmarketplacedemands">
    Operations to fetch information about marketplace advertisers.
  </Card>

  <Card title="Offers" icon="tag" href="/api-reference/get-partnersoffersrunnable">
    Operations for offers.
  </Card>
</CardGroup>