Introduction
The Verve Retail Media platform lets you serve ads to retail (DOOH) screens and manage the physical inventory those screens belong to. Integration happens over two REST APIs.
The APIs
Section titled “The APIs”| API | Auth | What it does |
|---|---|---|
| Ad API | Public | Request ads for a player, report playback exposure, and send signals. |
| Inventory API | OAuth 2.0 | Register and update locations and devices via idempotent upsert endpoints. |
Authentication at a glance
Section titled “Authentication at a glance”- The Ad API is public — no access token, no namespace header. The only identifiers are the
key+playeridcarried on the request itself. - The Inventory API is protected — every call needs an OAuth 2.0 access token and the
X-Verve-Namespaceproject header.
See Authentication for the full flow.
Endpoints
Section titled “Endpoints”You receive one set of endpoints per environment at onboarding. The development environment:
| API | https://api.dev.retailmedia.verve.com |
| Token | https://auth.dev.retailmedia.verve.com/oauth/v2/token |
Next steps
Section titled “Next steps”- Authentication — obtain and use an access token (Inventory API).
- Quickstart — make your first authenticated call end to end.
- API Reference — the full, generated endpoint reference.