Xpress v1 · approved partners

Serve Xpress ads
outside our apps.

The Xpress v1 surface lets approved partners request ad decisions, export VAST/VMAP, and report signed playback events from their own players, live productions, and placements.

Who qualifies

API and embed access is not automatic on any account tier. It is an eligibility offered through Platform+ and granted by approval, per application. Eligibility, inventory access, credits, campaign approval, placements, and API access are reviewed and approved by Xpress.

What the v1 surface does

Ad decisioning

Request an ad for a specific Xpress group, or run-of-network where your account is entitled. The v1 surface returns the winning creative along with its playback and tracking metadata.

VAST / VMAP export

Approved partners can export decisions as standard VAST or VMAP documents so Xpress inventory plays inside an existing player or ad stack, including live production tooling.

Signed tracking

Impression, quartile, completion, click, and error events are reported back through signed tracking URLs issued with each decision. Events reconcile against campaign reporting in the portal.

Integration overview

1

Get approved

API and embed access is granted per account, normally on Platform+. Xpress reviews the intended surface, expected volume, and content context before issuing credentials.

2

Receive credentials

Approved partners receive an application identifier and secret out of band. Credentials are never displayed in this portal and must stay on your server — never in browser or client code.

3

Request a decision

Your server calls the Xpress v1 decision surface with your application identity, the target group or a run-of-network request, and the placement context (position, duration, content type).

4

Play and report

Play the returned creative, then fire the signed tracking events at the appropriate playback milestones. Delivery and reporting appear in the partner portal.

Endpoint hosts, request schemas, and credential handling are provided in the partner integration packet once access is approved. Never place Xpress credentials in client-side code, a public repository, or a browser bundle.

Request surfaces

Group request

Ask for a specific Xpress ad group — event sponsors, a publisher's self-sold group, or a scheduled time-block group.

Run-of-network

Let Xpress select from eligible active ads already in rotation. RON is not a separate inventory bucket and it does not bypass entitlement.

Live insertion

Drive ad breaks in OBS or a live production workflow through Xpress Live Ads. Approved separately from standard video access.

Embed

Render an approved Xpress placement inside an external page or app surface, where the account is entitled.

Ready to integrate?

Tell us the surface you're building — external player, live production, or embedded placement — and we'll review your account for v1 access.