> For the complete documentation index, see [llms.txt](https://docs.blueseasx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blueseasx.com/server-bidding/introduction.md).

# Introduction

The following guide is for mediation partners who implement BlueSea as their certificated bidding partner.

Like most ad networks, BlueSea provides a similar server bidding orchestration approach. Please see the following workflow

<img src="/files/OB1R8IfwvnnpppLmgpK7" alt="" height="356" width="781">

1. The app initializes the mediation SDK
2. Mediation handles initialization of BlueSea SDK
3. The mediation SDK obtains a token from BlueSea SDK
4. The app requests an ad from the mediation SDK
5. The mediation SDK passes the token to its server
6. The mediation server constructs an oRTB request with the token, and passes them to BlueSea Server
7. BlueSea server returns an ad with encrypted adm and other necessary parameters in an oRTB response format
8. When BlueSea loses, the mediation server triggers lurl returned from BlueSea, while BlueSea wins, the server triggers nurl and passes the encrypted adm to its mediation SDK
9. The mediation SDK calls BlueSea SDK and passes the adm to load the ad creatives.&#x20;

Overall, on the client side:

* The mediation needs to obtain a token generated by BlueSea SDK and this is later passed to BlueSea server via oRTB request
* The mediation needs to pass the encrypted adm returned from BlueSea Server to BlueSea SDK to fetch ad creatives, if success, then it’s eligible for displaying

While on the server side:

* The mediation needs to follow BlueSea’s instruction and pass the required parameters when constructing an oRTB request
* The mediation needs to trigger nurl and lurl properly
* The mediation needs to parse the adm and send it the SDK