Displays
Displays is the Motionworks OOH display asset library product family (ADR-0043). It provides self-service, pay-as-you-go creation and measurement of individual out-of-home display faces through the Motionworks API v2. Each asset progresses through a synchronous lifecycle from draft to a final, published measurement.
The Displays API surface is exposed through REST endpoints on the Motionworks API v2 base (https://api2.mworks.com) under the /v2/displays/* path. The full endpoint-by-endpoint reference is auto-built from the OpenAPI spec at Displays API reference.
Displays On Demand is the self-service asset library mode: you create individual face assets through the API and purchase draft and final measurements on a pay-as-you-go credit basis. Each asset progresses through a lifecycle from draft to draft_measured to final_measured, with a display_id minted at the final stage. See Displays On Demand for the overview and endpoint map.
Displays Search lets authenticated callers find display assets by a closed filter set (media type, classification, digital flag, place type, and result limit) at a flat 1 credit per call.
Displays Maptiles delivers the Displays modeled-exposure geometry as Mapbox Vector Tiles (MVT) through a grant-based access pattern, covering six layers: faces, viewsheds, paths_vehicle, paths_pedestrian, gates_vehicle, and gates_pedestrian.
- On Demand asset library + Maptiles Products
- Per-asset draft and final Measurement
- Self-service API, credit-metered Access
Products
Who uses Displays
- OOH operators and media networks use the Displays asset library to create and measure individual faces on demand, without waiting for a monthly inventory publication cycle.
- Media buyers and agencies use Displays Search to find display assets by media type, classification, and place type, and purchase measurements for specific faces of interest.
- Developers and map engineers use Displays Maptiles to render modeled-exposure geometry (viewsheds, paths, gates) in MapLibre GL and compatible map clients.
Data dimensions at a glance
| Dimension | Coverage |
|---|---|
| Geographic coverage | United States (all markets); roadside and place-based inventory |
| Geographic resolution | Face-level (viewshed-precise); market roll-ups by county, state, CBSA, DMA |
| Asset lifecycle | draft, draft_measured, final_measured |
| Delivery | REST API (synchronous create, poll, read) + MVT tile surface |
| Pricing | Credit-metered per operation (see Purchase flow) |
Methodology summary
Displays uses the same viewshed methodology as the Viewcast family. The viewshed geometry, traffic source, and impression model are identical. What differs is the delivery model (self-service API vs. subscription feed), the identifier lifecycle (display_id minted at final_measured), and the scope of the tile surface. For the full geometric and traffic model, see Viewcast Methodology.
Full methodology: Methods: Viewcast
Jobs this family powers
- On Demand Measurement: Measure the delivered impressions (Circulation, OTS, LTS) for an individual OOH display face that you define and create through the API.
- Asset Creation: Create, refine, and archive individual display assets with anchor geometry, classification, and display attributes.
- Tile Rendering: Render modeled-exposure geometry as vector tiles in web map clients for planning and visualization.