AdQuick supports media owner integrations that enable automated inventory delivery, live availability, and streamlined booking workflows.
This article covers how integrations work, the standards AdQuick follows, and the questions media owners ask most often when starting the process.
Integration Framework
AdQuick follows the IAB OpenDirect specification for inventory and availability integrations. OpenDirect provides a standardized way for media owners to exchange inventory, availability, pricing, and order data with buying platforms.
The full specification is available as an external resource: OpenDirect v2.1.
What Can Be Integrated
Component | What it delivers | Required |
Inventory Feed | Your units, locations, specifications and pricing, so they display accurately on AdQuick. | Yes |
Live Availability | Open and booked dates, so buyers see what is actually available. | Yes, live or batch |
Order Delivery | Holds and orders pushed directly into your system. | Optional |
*Note: These can be implemented in phases. Most partners begin with an inventory feed and an availability endpoint, then add order delivery later if they want it.
Inventory Feed
You provide an API endpoint or structured data feed that includes:
Media type and unit details
Locations or routes
Dimensions and specifications
Audience data, if available
Pricing information, rate card or dynamic
Creative restrictions
Market coverage details
Live Availability
Availability is transmitted through your API following OpenDirect standards, which lets AdQuick retrieve:
Up-to-date open and booked dates
Availability rules, such as blackout periods
Minimum booking windows
Unit hold and reservation logic, if applicable
*Note: If live availability is not supported, AdQuick can consume scheduled batch updates instead.
Order Delivery (Optional)
Some partners choose to accept orders through the OpenDirect specification. This allows AdQuick to:
Place orders directly with you
Receive confirmations and counter-offers
Retrieve invoice and flight details, where supported
Step 1: Technical Scoping
AdQuick reviews your existing API or data structures to determine:
Which OpenDirect endpoints you support
Any custom fields or business rules
Update frequency for inventory and availability
Authentication method — OAuth, API keys, or similar
Step 2: Mapping And Data Alignment
AdQuick maps your data into the AdQuick inventory schema, covering unit types, subtypes, geolocation, measurement units, and pricing structures.
Clear mapping is required for accurate display and booking logic on the platform.
Step 3: Testing And Validation
AdQuick runs test calls against your endpoints to confirm:
Correct formatting
Complete field mapping
Accurate availability responses
Proper authentication flow
Order delivery, if applicable
Step 4: Go Live
Once validated, your inventory is published on AdQuick and availability checks become automated through your API or feed.
Required Data Fields
At minimum, AdQuick needs:
Unit ID
Media type and subtype
Exact location or route
Dimensions
Availability dates
Rate card price
*Note: AdQuick provides the full schema during onboarding.
How Often Availability Should Update
Frequency | Assessment |
Real time, via API | Preferred |
Hourly or daily batch updates | Accepted |
Less frequent than once per day | Not recommended |
Common Questions
Do I need to fully support OpenDirect to integrate?
No. AdQuick supports partial OpenDirect implementations. Many partners begin with an inventory feed and an availability endpoint, and add order delivery later.
Can we integrate without APIs?
Yes. AdQuick can consume static or scheduled batch feeds, such as daily S3 or FTP drops. This will not provide real-time availability.
Does AdQuick push holds or reservations back to us?
If you support OpenDirect order endpoints, AdQuick can push holds, orders, confirmations, and rejections. This is optional and configured during scoping.
What resources do media owners typically need?
Usually a technical contact who can maintain API feeds, access to your inventory and availability systems, and internal approval from operations or sales for automation workflows.
How long does an integration take?
Typically 2 to 6 weeks, depending on API readiness, the number of media formats, and internal turnaround time for testing.