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 :
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.
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.
In other words, using the Marketplace API is actually optional, since API users are free to access the Affiliate API directly :
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 directly. For example, more filters will be offered on reporting and offer endpoints.
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 :
- Fetch the API key associated with each brand the partner is connected with through this endpoint
- Use the Affiliate API to accomplish the required task
