Pinterest API Review: Access, Limits and What It Does

The Pinterest API is five products under one name, and only one of them lets you start today without an app review. Here is which one, and what the others ask for.

Try Supapush → Official site

Five products wearing one name

Pinterest's developer platform presents a single API, but the use cases it lists are effectively separate products with separate access paths. Conversions covers sending purchase and signup data back to Pinterest for optimisation and reporting. Content covers building apps that create and manage organic Pins and boards on a user's behalf. Ads covers campaign management, targeting setup and performance reporting. Catalogs, marketed as the Pinterest API for Shopping, handles product feeds and shopping ads. Analytics covers pulling content and ad data into your own warehouse. Deciding which of the five you need is the first real decision, because the approval requirements differ sharply between them and picking the wrong entry point costs weeks.

The one door that opens without approval

Here is the detail buried in Pinterest's help documentation and absent from most write-ups. The Conversions API does not require an application or a valid app ID. Anyone with a Pinterest Business account can start calling the POST send conversions endpoint, as long as they have generated a token from the Conversions page in Ads Manager. That is genuinely unusual and it means an advertiser can ship server-side tracking without waiting on a developer review. The limit is equally explicit: having a Business account does not automatically grant access to the wider Pinterest API. So Conversions is a fast lane, not a back door into content or ads endpoints, and planning a roadmap on the assumption that one implies the other will go badly.

What a conversions integration actually involves

Pinterest offers two routes. A third-party partner integration works if you already use one of its partner platforms, and a direct integration gives the most control but needs developer time. The timeline Pinterest quotes is honest and wide: as little as a few hours, or as long as a few weeks, depending which route you take. Four things decide whether the integration is any good. Pass data in real time, meaning under an hour, or real-time optimisation and attribution do not work. Pass the event_id parameter if you also run the Pinterest Tag or a mobile measurement partner, or your conversions get double-counted. Fire a test event and read the response codes back. Then watch Event Quality Score and aim for Good, because a working integration and a useful one are different things.

Getting onto the wider platform

Everything outside Conversions starts at the developer account setup flow, which you reach with a Pinterest business login rather than a personal one. Pinterest maintains an official quickstart repository on GitHub with runnable examples, which is a faster way into the request shapes than reading reference docs cold. Read the developer guidelines and the developer and API terms before you build, because what an app is permitted to do with user content is the part that gets integrations rejected rather than anything technical. There is a community forum for the questions docs do not answer. Pinterest has also announced an MCP server as on the way, aimed at letting agents call the platform directly, though at the time of the snapshot behind this page it was previewed rather than shipped.

When the API is not the answer

A lot of people searching for this API want something simpler than an integration: get a week of Pins scheduled, keep Pinterest in step with the other channels, and see which posts worked. Building that on raw content endpoints means writing an OAuth flow, a scheduler, a retry queue and an analytics rollup before you publish anything at all. Supapush is a multi-account composer covering ten networks with scheduling, a queue, a calendar and analytics already built. It is not a developer platform and will not send conversion events. If your actual requirement is publishing rather than programming, that distinction saves a month, and you can still add the Conversions API separately since it needs no app approval.

What you actually get

Building against the API versus using a composer

Shipping a conversions integration

1. Generate the token in Ads Manager
   Open the Conversions page in Ads Manager with a Pinterest Business account and create a token. No app registration is involved for this product specifically.
2. Choose direct or partner
   A partner integration is faster if you already use one of Pinterest's partner platforms. A direct integration gives more control and needs developer time. Pinterest quotes hours to weeks.
3. Send event_id with everything
   If the Pinterest Tag or a measurement partner is also firing, event_id is what stops the same conversion being counted twice. Check the deduplication view in Events Overview afterwards.
4. Fire a test event and read the codes
   Validate in Events Manager rather than assuming. Response codes come back per request, and Event Quality Score tells you whether the data you are sending is good enough to optimise on.

FAQ