Introducing the Peach Developer API

Peach is on a mission to modernise the ad ecosystem. There's still far too much manual reentry of campaign metadata and media plan info — and too much downloading and uploading of files between systems. We want to solve this.

We’re proud to announce that, as of today, it’s even easier to create and distribute video campaigns around the world. 

How so?

We’re excited to launch the Peach Developer API — a brand new product that makes it simple for the ad world to integrate in–house or 3rd party software with the Peach platform. 

Unlike many platforms, we don't want you to spend more time in our app, we want you to spend less. Why? Because that means you're getting your job done faster — so you can focus on more creative or strategic aspects of your day. We want to modernise the whole ad ecosystem — reducing the manual work and reducing errors. The Peach Developer API is a key part in making this happen. We can’t wait to get it into our client’s hands and see what can be created with it. 

So what does the Peach Developer API do? This release of the API is designed to programmatically (ad tech folk, this time we mean the original ‘programmatic’ not that other ‘programmatic’) integrate metadata and video assets via public links, then files are quality checked and distributed to broadcasters and platforms. 

Here are some examples of what can be done.

Automate advertising data

Got an internal system at your agency holding your media plan, assets and metadata? Automatically create campaigns, with ad metadata and destinations in Peach to distribute to broadcasters and other destinations.

Faster asset distribution

Stop uploading and downloading files between different ad platforms — with the Peach Developer API a video asset can be pulled into a campaign directly through a public URL. So if the video is on Dropbox, Google Drive or an asset management system they can be directly pulled in, QCed and renditions sent on to destinations — saving you huge amounts of time and avoiding costly mistakes.

Distribute to 40,000+ broadcasters, ad platforms and more

Simplify the distribution of video assets to broadcasters and other destinations. The naming of broadcasters and other destinations can often be inconsistent across the industry and can cause problems — using smart aliases the Peach Developer API works around this.

Developers: what you need to know

1. The Peach Developer API will initially support automation and integrations for the ‘buy–side’ of the Peach Platform: including creating campaigns, ads and destinations
2. The API is organized around common REST principles using standard HTTP response codes, authentication and verbs. All requests should be made over SSL. All request and response bodies, including errors, are encoded in JSON.
3. The initial feature-set provides CRUD functionality for basic entities: Campaigns, Ads, Assets and Destinations.
4. We’ve provided a set of mapping endpoints allowing you to use custom names for Advertisers, Brands, Destinations and Channels
5. Video assets can be added into campaigns via public URL (e.g. via Dropbox, Google Drive, asset management systems, etc.)
6. The API’s data mocking feature allows you to test the APIs using a predefined set of IDs interconnected and synced between all exposed entities – this limits the amount of time needed to integrate with Peach and removes the need of using a test account. 
7. The rich documentation covers every available endpoint (detailing both requests and responses) and includes a Postman collection providing full–suite test coverage.
8. Currently the API supports distribution to our huge range of ‘direct destination’ integrations covering broadcasters around the world. It currently excludes activator destinations and ones that require user authorisation. 

For lots more information developers can visit the Peach Developer API page and follow the instructions for registration, authentication and authorization, or contact us for more information.

The Peach Developer API has been many years in the making. The Peach app itself is built on a rich API layer which iterated on a version launched in 2016 and used internally. This is battle hardened stuff. But it takes a lot more to be externally facing, so I’d like to thank Clinton Van Ry, Bartosz Gosiewski and the entire team who built it, the clients who helped us define how it should work and tested earlier internal versions, plus the many people who were excited about the possibilities it would create — including some Peach alumni such as Tadas Tamošauskas, Frank Lakebrink, Tom Walne and many others.