Ad API Guide

about

About this site

Who writes Ad API Guide, how it is funded, and how relationships with the routes it compares are handled.

Last updated 2026-09-15

Ad API Guide answers one question: how do you get advertising-library data into a research workflow, and what can that data actually tell you. It is written for growth teams and agent builders who want to see what competitors are running on Meta, Google, TikTok and LinkedIn without maintaining scrapers, and who need to know which routes are permitted, which fields are real, and what each call costs.

Who writes here

Pages are written and re-checked by Shirley Lou, who runs the data-API research behind this site. There are no pseudonymous authors on this site.

Relationships {#relationship}

This site is run independently of the providers it compares, with one relationship to state: the people who run it also work on Treg, a pay-per-call API that routes data requests across providers, and Treg appears in some comparisons as one route among others. Every page that includes a Treg route says so in a note at the end of the page. Every Treg figure is a call we paid for, with the raw response downloadable, and the same fixture is run against the alternatives where their terms allow. Provider prices are quoted from each provider’s own pages with the URL and date next to the number. No affiliate links, no paid placements, no rankings.

What is not on this site

  • No claims about competitors’ ad spend. Public ad libraries do not expose spend for ordinary commercial ads, and no route can conjure it.
  • No “best ad library API” rankings. Each page reports what a route returned on the cohort and says who it fits.
  • No affiliate links.

Corrections

If a fact, price or access term on this site is wrong, email corrections@adapiguide.com with the page and a source. Changes are logged on the corrections page.