Expert user? Allergic to lengthy documentation sites? Follow these steps:
adDrop.com.au has created a RESTful API that can be used by ACM customers wanting to integrate their internal systems directly into the ACM advertising production workflow. This will make the process of submitting advertising content a lot easier. Before you can start using the adDrop.com.au API you will need a client_id and client_secret. These are used to obtain a temporary key (bearer token) that is used to authenticate every API call.
The adDrop API provides 2 primary functions. The first is it provides the ability to retrieve booking information about a specific advertisment directly from the ACM booking system. This data will provide specific booking details like the height and width, bleed, stock type and colour values. It also contains insertion details and the final deadline time that content will be accepted for the booking. Secondly it provides a mechanism to POST advertising material against an ACM booking. The material must be a PDF file and the file will be validated and checked before it is accepted into the ACM production system. Any erroneous files or validation errors will be passed back through the API repsonse message.
Click here to watch the Query Booking API endpoint in action using Postman.
Click here to watch the Upload Material API endpoint in action using Postman.
The root URL of the API is located at:
The adDrop.com.au API is secured using OAUTH therefore in order for you to start querying data you will first need to obtain a <client_id>
and <client_secret>
. Depending on your unique access requiments, the key will allow you to interact with data for specific ACM customers.
A client_id and client_secret can be requested by emailing api@addrop.com.au.
Every time you make a query the response is returned as an object serialised using JSON encoding.
All data is returned as UTF-8 JSON. Some characters may be escaped as \uXXXX
, as described in the JSON specification: http://www.json.org/
If your request cannot be handled, an HTTP response code other than 200 will be returned and the error will be serialised in the serialisation format requested. More details on the Interactive Endpoint Documentation.