Get your Placement ID

Every live Offer Query and MCP call is identified by a placement id (plc_…). The placement belongs to one of your Applications, so traffic and earnings are attributed to that Application.

For how to send it, see Authentication. That page is the authority for identity mechanics; this page explains where the placement id comes from.

Run the Public Test Sandbox

When you already have an enabled account

Only a serviceable Application serves live traffic. In the Developer Portal, open the Application, go to Placements, create a placement for the surface where offers appear, and copy its placement id. This documentation does not promise that an account can self-serve its own activation or access.

Open Developer Portal for an enabled account

Access handoff boundary

You are ready when you have the placement id of a placement in a serviceable Application. That placement id is all Offer Query and MCP need. Send it in the X-AON-Placement-Id header. It is not a secret, so it can ship in a browser, web view, or app. Pulling performance data is a separate step; see the Reporting API. Live completion remains the successful route-specific query, not this access handoff.

When your account is not enabled

Public contract documentation cannot confirm account eligibility or activate an account. You can still validate the Query shape in the Public Test Sandbox. Return to Authentication once your account is enabled; this page does not define an application or invitation flow.

Without a placement id

A placement id is recommended, not required. An Offer Query or MCP search with no placement id is served anonymously through the AON default placement: the response carries extra.identity.mode="anonymous", and anonymous traffic earns no attribution or earnings. An API key does not supply the placement: an unmapped live key without a placement is served anonymously with an extra.key_notice, and a non-sandbox aon_test_ key without a placement returns 401 UNAUTHORIZED. API keys are for the Reporting API, OfferInfo API, Offer Instance API, account routes and the public test sandbox. The aon_submit_feedback and aon_manage_watch MCP tools require an active X-AON-Placement-Id header, with no API key.

Local SDK verification

SDK mock mode uses local data to verify API shape. It does not need a placement id and does not create runtime eligibility.

With a placement id, continue with the REST / HTTP route, SDK route, or MCP route that matches your integration.