Prebid Server | Endpoints | /info

• GET /info/bidders
• GET /info/bidders/{bidderName}
• GET /bidders/params

GET /info/bidders

This endpoint returns a list of Bidders supported by Prebid Server. These are the core values allowed to be used as request.imp[i].ext.{bidder} keys in Auction requests.

For detailed info about a specific Bidder, use /info/bidders/{bidderName}.

Sample Response

This endpoint returns JSON like:

["msft","audienceNetwork","pubmatic","rubicon","other-bidders-here"]

GET /info/bidders/{bidderName}

This endpoint returns some metadata about the Bidder whose name is {bidderName}. Legal values for {bidderName} can be retrieved from the /info/bidders endpoint.

Sample Response

This endpoint returns JSON like:

{"maintainer":{"email":"info@prebid.org"},"capabilities":{"app":{"mediaTypes":["banner","native"]},"site":{"mediaTypes":["banner","video","native"]},"dooh":{"mediaTypes":["banner","video","native"]}}}

The fields hold the following information:

• maintainer.email: A contact email for the Bidder’s maintainer. In general, Bidder bugs should be logged as issues… but this contact email may be useful in case of emergency.
• capabilities.app.mediaTypes: A list of media types this Bidder supports from Mobile Apps.
• capabilities.site.mediaTypes: A list of media types this Bidder supports from Web pages.
• capabilities.dooh.mediaTypes: A list of media types this Bidder supports from Digital Out Of Home (DOOH)experiences.

GET /bidders/params

This endpoint gets information about all the custom bidders params that Prebid Server supports.

Returns

A JSON object whose keys are bidder codes, and values are Draft 4 JSON schemas which describe that bidders’ params.

For example:

{"msft":{/*Ajson-schemadescribingMicrosoft'sbidderparams*/},"magnite":{/*Ajson-schemadescribingRubicon'sbidderparams*/},"otherBidder":{/*Ajson-schemadescribingRubicon'sbidderparams*/}}

The exact contents of the json-schema values can be found at github.com/prebid/prebid-server/tree/master/static/bidder-params