Pinterest Ads

Overview

Pinterest Ads data synced to V4MOS.AI, through the integration's own endpoints

The V4MOS.AI Pinterest Ads API gives you the raw records synced from the Pinterest Ads accounts connected to your organization: ad accounts, campaigns, ad groups, ads and their daily analytics. Rows come as they were synced, with the warehouse column names (snake_case), so you can load them straight into your BI. All endpoints use the /v1/pinterest-ads prefix and the same authentication, pagination and response format.

Getting started

Base URL: https://data.v4mos.ai. Every call requires your API credentials and the organizationId — see Authentication.

  1. Connect Pinterest Ads in app.v4mos.ai (Connected accounts) and wait for the first sync.
  2. Call any endpoint below with your organizationId, for example GET /v1/pinterest-ads/ad-accounts?organizationId=….
  3. Every row carries integration_id and integration_name: the connected account it came from. To read a single account, pass that value as integrationId.

Available endpoints

Resources

EndpointWhat one row isdateFrom / dateTo filter
GET /v1/pinterest-ads/ad-accountsOne row per ad account: name, country and currency. Times are epoch seconds.—
GET /v1/pinterest-ads/campaignsOne row per campaign: status and objective.—
GET /v1/pinterest-ads/ad-groupsOne row per ad group, with its campaign and status.—
GET /v1/pinterest-ads/adsOne row per ad, with its ad group, campaign and status.—
GET /v1/pinterest-ads/campaigns-analyticsOne row per campaign per day: spend, impressions and clicks, plus every other metric Pinterest reports in metrics (JSON).date
GET /v1/pinterest-ads/ad-groups-analyticsOne row per ad group per day: spend, impressions and clicks, plus every other metric Pinterest reports in metrics (JSON).date
GET /v1/pinterest-ads/ads-analyticsOne row per ad per day: spend, impressions and clicks, plus every other metric Pinterest reports in metrics (JSON).date

Pagination and filters

  • page (default 1) and limit (default 500, max 5000). meta.hasNextPage says whether another page exists; rows come in a stable order, so walk the pages until it is false.
  • dateFrom / dateTo (YYYY-MM-DD, inclusive) filter by the date column shown in the table above. Resources without one reject them.
  • integrationId keeps the rows of one connected account.
  • Answers are cached for 30 minutes and the data is synced once a day — see Data sync.

Response format

{
  "data": [{ "...": "one object per row, with the columns listed on each endpoint" }],
  "meta": {
    "page": 1,
    "limit": 500,
    "hasNextPage": true,
    "hasPreviousPage": false
  }
}

Amounts and large counters (fields with format: decimal or format: int64 in each endpoint schema) come as strings, e.g. "125.50", so no precision is lost. Convert them to a decimal type on your side.

On this page