For teams that want AdQuick inside their own workflows rather than alongside them, API access is available.
What can the API do?
The API is REST-based over HTTPS, returns JSON, and covers four resources: campaigns (list, create, book, retrieve), advertisers (list, create, retrieve, update), media types (the standard OOH format list), and reports (campaign-level and plan-level, returned as CSV). Both direct and programmatic campaign types are supported, so OOH performance can sit next to your other channels in the systems you already use.
Common integration patterns
BI and dashboards: Campaign delivery and measurement data into Looker, Domo, Tableau, or your warehouse for unified cross-channel reporting.
CRM and sales systems: Campaign data alongside pipeline data for teams tying OOH to account-based motions.
Product embedding: Partners building OOH capability into their own client-facing products.
How do I get access?
API access is provisioned through your AdQuick team, who will scope your use case, issue your Partner ID and credentials, and confirm any applicable terms. Requests authenticate with a bearer token plus a partner token in the headers.
How deep does vendor coverage go through the API?
Data coverage follows the marketplace's inventory relationships, spanning major operators and beyond. If your use case depends on specific vendors' data (particularly outside the largest operators), verify coverage for those vendors during scoping rather than assuming.
If you don't need an API
All reporting is exportable from the platform in standard formats, which covers most periodic-reporting needs without engineering work. The API earns its setup cost when data needs to flow automatically and continuously.