Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Synchronizing Your Inventory Using the Console API

Whether you use AppNexus Supply Integration (ASI) or OpenRTB integration, you'll synchronize your inventory by mapping your publisher and placement fields to Console API publisher and placement fields.  You use the Console API to do the following:

  1. Create a new publisher that's mapped to your publisher.
  2. Create a new placement group.
  3. Create a new placement that's mapped to your placement.
  4. Test the mapping with a debug auction. (Optional.)
On This Page

Before You Begin

Before you begin, you must meet the following criteria:

Bid Request Fields

Console API ServiceConsole Service Field ASI FieldOpenRTB Field
Publisher codeext_pub_codeBidRequest.Site.Publisher.id
Placementcodeext_placement_codeBidRequest.Site.id

If you use custom integration types, you can contact AppNexus Support to learn how your bid requests map to AppNexus publishers and placements.

The following steps will explain how to create publisher and placement objects with the proper configuration to accept those mappings.

Step 1. Create a Publisher

Use the Publisher Service to create a new publisher that's mapped to your inventory.   Use the value for ext_pub_code or BidRequest.Site.Publisher.id as the publisher code. 

is_oo is an optional field that indicates the publisher is owned and operated by the network (100% of the revenue goes to the network).

reselling_exposure is an optional field that indicates whether you would like to expose the publisher's name to buyers (public or private).

The API returns the ID of the newly created object in its response.  Save this value for use in the next two steps.

Step 2. Create a Site (Placement Group)

Use the Site Service to create one or more sites (or placement groups).  Sites are simply a grouping mechanism for placements.  At least one site is required, but you don't need to create additional ones if you don't need further granularity.

Supply type options are:

  • web: Desktop browser inventory 
  • mobile_web: Mobile browsers
  • mobile_app: Mobile applications

Step 3. Create a Placement

Use the Placement Service to create placements, which are the most granular sell-side objects.

Step 4. Test the Mapping Setup (Optional)

You can test that the mapping is working correctly by using a debug auction.  Send a test impression to our endpoint with the debug paramenters and check that the impression reaches the expected placement.


  • No labels