Ad screenshot APIs: how they work and what to look for

What an ad screenshot API returns, how it differs from a website screenshot API, and what to check before you integrate

Landon Bennett, Co-Founder & CEO of Ad Reform
Landon Bennett

Updated

An ad screenshot API is a service your software calls to get screenshots of an ad running on real web pages. You send the creative and a list of sites and devices. The service places the ad into a matching ad slot on each page and sends back images of the ad in context, with the page URL, a timestamp and a device frame. That last part is the difference from a general website screenshot API, which captures whatever happens to load and can’t put your specific creative into the slot.

How an ad screenshot API works

  1. You send a request with the campaign name, the ad, and the screenshots you want, each one a site and a device.

  2. The service loads each page in a real browser at that device’s size, finds an ad slot that fits the creative and places the creative there.

  3. It captures the right moment. For video and HTML5 you choose the frame. In Ad Reform you can set frame timestamps from 0 to 30 seconds.

  4. Every screenshot is checked. Ours go through an AI agent first, and our team reviews any that fail.

  5. Results come back by webhook as image URLs you can store, show in your own product or turn into a deck.

The Ad Reform API docs show the full request and webhook format.

What it should support

  • Formats: images, video, VAST tags, HTML5 (zip files by URL) and raw HTML ad tags.

  • Channels: display, video, native, in-app and newsletter placements.

  • Devices: desktop, mobile and tablet, ideally with named devices such as iPhone, iPad, Pixel and Galaxy.

  • Context on every image: browser URL, timestamp and device frame, so a screenshot works as proof.

  • Output beyond images: branded PowerPoint or PDF decks, and standalone ad previews before a campaign goes live.

Ad screenshot API vs. website screenshot API

Ad screenshot API

Website screenshot API

What it captures

Your creative, placed into an ad slot on the page

Whatever loads on the page at that moment

Rotating and programmatic ads

Places the ad you asked for

Depends on luck and repeated loads

Blank slots and bot blocking

Handled and checked

Returned as is

Review

Checked before delivery

None

Built for

Proof of placement and ad previews

Page captures, thumbnails, archiving

Website screenshot APIs are good tools for what they’re built for. They just don’t solve the ad problem. We compare specific tools in ad screenshot API vs. screenshot APIs.

Who uses an ad screenshot API

  • Ad platforms and DSPs that offer screenshots to their own customers inside their product. DeepIntent and Teads use our API this way.

  • Agencies that build screenshots into their own reporting.

  • Publishers and retail media networks that want recaps generated from their own systems.

If you’d rather not write code, our integrations with Google Ad Manager, DV360, CM360, The Trade Desk and Xandr pull campaigns in directly.

What to check before you integrate

  • Placement: does it place your creative, or only capture pages?

  • Delivery: does it push results by webhook, and what happens if your endpoint is down? Ours retries a failed delivery up to 14 times over about 24 hours.

  • Quality: who checks the screenshots before you get them?

  • Docs: can your developers read the full API reference before signing anything?

  • Your brand: can you show results inside your product or decks under your own name?

  • Pricing at volume: what does your busiest month cost?

Should you build your own?

Building looks simple: a headless browser and a crop. The real work is finding ad slots across thousands of different site layouts, getting past consent banners, lazy loading and bot blocking, and checking every output so a blank slot never reaches a client. We wrote about why in don’t build your own ad screenshot tool.

FAQ

What is an ad screenshot API? A service your software calls to get screenshots of an ad placed on real web pages, on the devices you choose, with the URL and timestamp on each image.

Can I use a regular screenshot API like Urlbox or ScreenshotOne for ad screenshots? You can capture pages with them, but you can’t choose which ad appears in the slot. For a specific campaign you’d be reloading pages and hoping. An ad screenshot API places the creative you asked for.

Does an ad screenshot API work for programmatic campaigns? Yes. Because the creative is placed into the page, it doesn’t matter which exchange or DSP served it. Ad Reform also connects to DV360, CM360, The Trade Desk and Xandr to pull campaigns in.

How are the screenshots delivered? By webhook. When a set is approved, the API sends the image URLs to your endpoint. Ours retries up to 14 times over about 24 hours if delivery fails.

Can it capture video and HTML5 ads? Yes. You choose the moment to capture, from 0 to 30 seconds into the ad.

Is an ad screenshot API the same as ad verification? No. It shows how and where an ad appears. It doesn’t measure impressions, viewability or fraud.

Wave goodbye to busywork

Don't waste another minute

join users in over 60 countries

A hand holding a pencil

Wave goodbye to busywork

Don't waste another minute

join users in over 60 countries

A hand holding a pencil

Wave goodbye to busywork

Don't waste another minute

join users in over 60 countries

A hand holding a pencil