Connect supplier inventory to Demand

Register and operate supply through the Partner API, then let buyers discover and transact through the existing Demand interfaces. Supplier identity, inventory catalogue, serving connection, availability and payment are separate facts on the same platform.

Register the organization and its screens

Follow the Partner quickstart. A new organization registers through:


curl --fail-with-body -sS https://api.trillboards.com/v1/partner/register \
  -H 'Content-Type: application/json' \
  -d '{"name":"Your Company","slug":"your-company-unique-slug","contact_email":"developer@your-company.example"}'

Save the returned data.api_key securely. Existing organizations use their existing account and key-management flow. Use the same partner account for device registration, inventory settings, reporting and webhooks. Do not infer authorization from a key prefix.


curl --fail-with-body -sS https://api.trillboards.com/v1/partner/info \
  -H "Authorization: Bearer $TRILLBOARDS_API_KEY"

curl --fail-with-body -sS https://api.trillboards.com/v1/partner/devices \
  -H "Authorization: Bearer $TRILLBOARDS_API_KEY"

Register and reconcile exact devices through the Partner reference. Preserve returned screen and device identities when adding an integration. Re-registering the same physical screen under another identity creates a different record rather than proving new supply.

Establish the actual serving connection

Choose the integration that matches the publisher's player:

A registered device, catalogue import, issued code or unused adserver tag is inventory setup. The connection becomes established after an accepted, verified interaction for that exact screen. A public poll or generic tracking event does not establish it.

The buyer class owned_and_operated means an established direct player, API or validated adserver connection. It applies to directly connected screens owned by Trillboards or another publisher. The partner class covers inventory without an established direct connection. Supplier ownership and catalogue source remain provenance; they do not assign class.

Ordinary connectivity outages change current readiness without reclassifying an established connection. Explicit device detachment changes the active binding; a separately established adserver connection can continue to qualify the same screen. Read current readiness and fulfillment information alongside class.

Publish usable inventory and follow its fulfillment route

Keep the canonical screen identity, location, dimensions, timezone, operating schedule, creative requirements and current availability accurate through the existing supplier interfaces. Buyers use the same catalogue and connection facts through advertiser inventory search and DSP discovery.

An imported external venue can be discovered before it has a direct serving connection. A successful purchase still follows that inventory's configured fulfillment route. A direct tag requires its exact connected, renderable screen. An owner IO can require publisher acceptance. An offered venue, a returned forecast or an adserver tag registration alone is not a paid reservation.

Preserve opaque IDs and legacy wire values containing vistar; they identify existing partner inventory records. Applications should use the advertised public fields and returned IDs without translating them into a new catalogue.

Report what actually happened

Use the issued playback and tracking contract for the chosen integration. Keep request, impression, creative and screen identifiers intact across serving and completion. Use the existing device playback, heartbeat, impression and partner reporting interfaces from the Partner reference rather than creating another delivery counter.

Buyer status reports the actual line state, including pending owner confirmation and partial stop results. Supplier delivery reports retain their reporting basis and freshness. Canonical completed plays, audience observations and partner reports can differ because they measure different events and windows; the buyer delivery response exposes their reconciliation.

Use the buyer journey, DSP journey and metric dictionary to verify the end-to-end result.