Overview
AdQuick supports media owner integrations that enable automated inventory delivery, live availability, and streamlined booking workflows. This article outlines how integrations work, what standards AdQuick follows, and the most common questions media owners have when beginning the process.
Integration Framework
AdQuick follows the IAB OpenDirect specification for inventory and availability integrations.
You can review the full OpenDirect 2.1 documentation here (external resource):
OpenDirect provides a standardized way for media owners to exchange inventory, availability, pricing, and order related data with buying platforms such as AdQuick.
What Can Be Integrated
AdQuick typically integrates the following components:
1. Inventory Feed
Media owners 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
Inventory feeds allow AdQuick to display accurate, up to date units in the platform.
2. Live Availability
Live or near real time availability is transmitted through the media owner’s API following OpenDirect standards. This enables AdQuick to retrieve:
Up to date open and booked dates
Availability rules (e.g., blackout periods)
Minimum booking windows
Unit hold and reservation logic (if applicable)
If live availability is not supported, AdQuick can consume scheduled batch updates instead.
3. Order Delivery (Optional)
Some partners choose to accept orders through the OpenDirect specification. This allows AdQuick to:
Place orders directly with the media owner
Receive confirmations and counter-offers
Retrieve invoice and flight details (when supported)
*This component is optional and can be implemented in phases.*
Integration Workflow
Step 1: Technical Scoping
AdQuick reviews the media owner’s existing API or data structures to determine:
Supported OpenDirect endpoints
Any custom fields or business rules
Update frequency for inventory and availability
Authentication method (OAuth, API keys, etc.)
Step 2: Mapping & Data Alignment
AdQuick maps the media owner’s data into the AdQuick inventory schema.
This includes:
Unit types
Subtypes
Geolocation
Measurement units
Pricing structures
Clear mapping is required for accurate display and booking logic in the platform.
Step 3: Testing & 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, the inventory is published on AdQuick, and availability checks become automated through your API or feed.
Common Questions (FAQ)
Do I need to fully support OpenDirect to integrate with AdQuick?
No. AdQuick can support partial OpenDirect implementations. Many partners begin with:
Inventory feed
Availability endpoint
And add order delivery later if desired.
Can we integrate without APIs?
Yes AdQuick can support static or scheduled batch feeds (e.g., daily S3/FTP drops).
However, this will not provide real time availability.
What data fields are required?
Minimum required fields include:
Unit ID
Media type and subtype
Exact location or route
Dimensions
Availability dates
Rate card price
AdQuick will provide a full schema during onboarding.
How often does availability need to update?
Preferred: real time via API
Accepted: hourly or daily batch availability updates
Not recommended: updates less frequent than once per day
Does AdQuick push holds or reservations back to us?
If the media owner supports OpenDirect order endpoints, AdQuick can push:
Holds
Orders
Confirmations
Rejections
This is optional and configured during scoping.
What resources do media owners typically need to integrate?
Usually:
A technical contact capable of maintaining API feeds
Access to inventory and availability systems
Internal approval from operations or sales teams for automation workflows
How long does the integration take?
Typical range: 2–6 weeks, depending on:
API readiness
Number of media formats
Internal turnaround time for testing
