Skip to main content

Pinterest API

Pinterest is a visual discovery platform where people find ideas through Pins and boards, and where businesses publish content, run ads and list their product catalogs. The Pinterest API connector reads the user account, boards, sections, Pins, ad accounts, campaigns, ad groups, ads, audiences, customer lists, keywords, catalogs, organic and ads analytics, and asynchronous ads reports, and can create, update and delete boards, sections, Pins, ads objects, audiences and catalog data.

Pinterest API icon

Power end-to-end data operations for your Pinterest API API with Nexla. Our bi-directional Pinterest API connector is purpose-built for Pinterest API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Pinterest API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Pinterest API workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Nexla connects to the Pinterest API v5 (https://api.pinterest.com/v5) as a Pinterest user, through a Pinterest developer app that you register. Complete the following steps before creating a credential in Nexla.

  1. Make sure you have a Pinterest business account. The ads templates also need access to at least one ad account, and the catalog templates need a catalog in the business account. Nexla can only read and change what the authorizing user can access.

  2. Sign in to developers.pinterest.com/apps with the business account, and connect (create) an app. Pinterest reviews new apps before it grants them API access.

  3. In the app's settings, add https://dataops.nexla.io/nexla-api/oauth/callback as a Redirect URI (or /nexla-api/oauth/callback on the Nexla host you sign in to). The redirect URI must match exactly.

  4. Copy the app's App ID and App secret key. You will enter them as the Client ID and Client Secret of the Nexla credential. Store the secret securely.

  5. To use the destination templates that create or change ads objects (ad accounts, conversion tags and events, campaigns, ad groups, ads, audiences, customer lists, targeting templates and keywords), or catalogs, the app needs Pinterest's approval for the ads:write or catalogs:write scope. Request it from Pinterest for your app. Once it is approved, add the scope to the Access Scope field of the credential.

Pinterest grants the scopes listed in Access Scope when you authorize the credential. If you change the scopes later, for example to add ads:write or catalogs:write, click Authorize again so that Pinterest issues a token with the new scopes. Until then, templates that need the new scope fail with an authorization error.

For complete details about apps, OAuth and scopes, see the Pinterest API documentation.

Some destinations publish content, spend money or delete data

Destination templates that create or change boards, sections, Pins and catalog items publish to the user's Pinterest profile; these are marked Publishes content below. Templates that create or change campaigns, ad groups, ads and keywords act on live advertising, and can start delivering ads and spending the ad account's budget; these are marked Spends budget. Templates that delete boards, sections, Pins, feeds, product groups, items or customer list members are marked Deletes data; deleted objects cannot be restored from Nexla. To create ads objects without spending, set status to PAUSED in the record.

Authenticate​

Credentials required​

FieldRequiredSecretDescription
Access ScopeYesNoPinterest API Access Scope
Client IDYesNoPinterest API Client ID
Client SecretYesYesPinterest API Client Secret for Token URL

Access Scope is a comma-separated list of Pinterest OAuth scopes. It defaults to ads:read,boards:read,boards:read_secret,boards:write,catalogs:read,pins:read,pins:read_secret,pins:write,user_accounts:read, which covers every source template and the board, section and Pin destination templates. The ads:write and catalogs:write scopes are not included, because Pinterest must approve them for your app first; add them once they are approved (see Prerequisites). The *_secret scopes let Nexla read secret boards and the Pins on them; remove them if Nexla should only see public content.

Pinterest requires the Client Secret to issue tokens. Nexla sends the Client ID and Client Secret to Pinterest's token endpoint in an HTTP Basic Authorization header, as Pinterest requires.

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Pinterest API

PinterestCred.png
  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  2. Enter the App ID of your Pinterest app in the Client ID field, and its App secret key in the Client Secret field.

  3. Review the Access Scope field. Keep the default, or add ads:write and catalogs:write if Pinterest has approved them for your app and you plan to use the ads or catalog destination templates.

  4. Click the Authorize button. Sign in to Pinterest as the user that Nexla should act as, and approve access. Nexla stores the refresh token and gets new access tokens automatically.

  5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Nexla tests the credential by reading the authorized user's account.

Keep the Client Secret confidential. If it is compromised, reset the app secret key in the Pinterest developer portal, update the credential, and authorize it again.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Pinterest API connector tile, then select the credential that will be used to connect to Pinterest, and click Next; or, create a new Pinterest API credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Pinterest API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area. The note under each group names the OAuth scopes it needs; all of them are in the default Access Scope.

Pinterest objects are nested: the user owns boards, a board holds sections and Pins, an ad account holds campaigns, a campaign holds ad groups, and an ad group holds ads and keywords. Most ads templates need an ad account ID: start with List Ad Accounts to find it, and use the matching list template to find any other ID a template asks for. Date settings use YYYY-MM-DD and UTC; analytics templates read at most 90 days back. Templates that say "Results are paged automatically" read every page; all other templates make a single request.

User account​

Reads the authorized user's profile, followers and verified websites. Needs user_accounts:read.

Get User Account

Retrieves the authorized user's profile: username, account type, business name, follower, following, board and Pin counts, and monthly views.

List Linked Business Accounts

Lists the business accounts linked to the authorized user, with each account's username and profile images.

List Followers

Lists the users who follow the authorized user.

List Following

Lists the users that the authorized user follows.

List Followed Boards

Lists the boards that the authorized user follows.

List Followed Interests

Lists the interests that a user follows.

  • Enter the Username: the username value returned by the Get User Account template.
  • See the Pinterest API reference for the response fields.

List Verified Websites

Lists the websites that the user has claimed, with each website's verification status and time.

Get Website Verification Code

Retrieves the meta tag, DNS TXT record and file content that the user can use to claim a website.

Boards​

Needs boards:read. Secret boards are returned only with boards:read_secret.

List Boards

Lists the boards that the user owns, with each board's name, description, privacy, and Pin and follower counts.

Get Board

Retrieves one board.

  • Enter the Board ID. Use the List Boards template to find it.
  • See the Pinterest API reference for the response fields.

Search Boards

Searches the user's boards by text.

Board sections​

Needs boards:read; reading the Pins in a section also needs pins:read.

List Board Sections

Lists the sections of a board, with each section's ID and name.

  • Enter the Board ID. Use the List Boards template to find it.
  • See the Pinterest API reference for the response fields.

List Board Section Pins

Lists the Pins in one board section.

  • Enter the Board ID. Use the List Boards template to find it.
  • Enter the Section ID. Use the List Board Sections template to find it.
  • See the Pinterest API reference for the response fields.

Pins​

Needs pins:read and boards:read. Pins on secret boards are returned only with pins:read_secret and boards:read_secret.

List Pins

Lists the Pins that the authorized user owns, with each Pin's title, description, link, board, media and creation time.

Get Pin

Retrieves one Pin with its title, description, link, board, media and creation time.

  • Enter the Pin ID. Use the List Pins or List Board Pins template to find it.
  • See the Pinterest API reference for the response fields.

List Board Pins

Lists the Pins on one board.

  • Enter the Board ID. Use the List Boards template to find it.
  • See the Pinterest API reference for the response fields.

Search Pins

Searches the user's Pins by text, or by a comma-separated list of Pin IDs.

  • Enter the search text, or a comma-separated list of Pin IDs, in the Query field.
  • See the Pinterest API reference for the response fields.

List Pin Product Tags

Lists the products tagged on a Pin.

  • Enter the Pin ID. Use the List Pins or List Board Pins template to find it.
  • See the Pinterest API reference for the response fields.

List Media Uploads

Lists the media uploads that the user has registered, with each upload's status.

Get Media Upload

Retrieves the status of one media upload: registered, processing, succeeded or failed.

  • Enter the Media ID: the media_id value returned by the List Media Uploads template.
  • See the Pinterest API reference for the response fields.

Ad accounts​

Ad accounts and the objects that belong to them directly: conversion tags, lead forms and order lines. Needs ads:read.

List Ad Accounts

Lists the ad accounts that the user owns or can access, with each account's name, owner, country, currency and permissions. Use it to find the ad account ID that most ads templates need.

Get Ad Account

Retrieves one ad account.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

List Ad Account Countries

Lists the countries where an ad account can be created, with each country's currency.

List Conversion Tags

Lists an ad account's conversion tags, with each tag's name, status, last fired time and enhanced match setting.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Conversion Tag

Retrieves one conversion tag with its code snippet.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Conversion Tag ID. Use the List Conversion Tags template to find it.
  • See the Pinterest API reference for the response fields.

List Page Visit Conversion Tags

Lists the conversion tags that have fired a page visit event.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get OCPM Eligible Conversion Tags

Lists the conversion tags that can be used for optimized CPM (oCPM) bidding, grouped by conversion event.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

List Lead Forms

Lists an ad account's lead forms, with each form's name, status, questions and privacy policy link.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Lead Form

Retrieves one lead form.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Lead Form ID. Use the List Lead Forms template to find it.
  • See the Pinterest API reference for the response fields.

List Order Lines

Lists an ad account's order lines (prepaid insertion orders).

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Order Line

Retrieves one order line.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Order Line ID. Use the List Order Lines template to find it.
  • See the Pinterest API reference for the response fields.

Campaigns​

Needs ads:read.

List Campaigns

Lists an ad account's campaigns, with each campaign's name, status, objective, budgets and dates.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Campaign

Retrieves one campaign.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Campaign ID. Use the List Campaigns template to find it.
  • See the Pinterest API reference for the response fields.

Ad groups​

Needs ads:read.

List Ad Groups

Lists an ad account's ad groups, with each ad group's campaign, status, budget, bid and targeting.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Ad Group

Retrieves one ad group.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Ad Group ID. Use the List Ad Groups template to find it.
  • See the Pinterest API reference for the response fields.

Get Bid Floors

Returns the minimum bids for a billable event, objective and targeting. This template sends a POST request, but it only reads data.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Bid Floor Request: the JSON request body, with bid_floor_specs (billable_event, currency, objective_type and so on) and, optionally, targeting_spec. Defaults to {"bid_floor_specs": [{"billable_event": "IMPRESSION", "currency": "USD", "objective_type": "AWARENESS"}]}.
  • See the Pinterest API reference for the response fields.

Estimate Audience Size

Estimates the audience size range for an ad group targeting spec. This template sends a POST request, but it only reads data.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Sizing Request: the JSON request body, with targeting_spec and, optionally, keywords, creative_types, placement_group and auto_targeting_enabled. Defaults to {"targeting_spec": {"GEO": ["US"], "AGE_BUCKET": ["25-34"]}}.
  • See the Pinterest API reference for the response fields.

Ads​

Needs ads:read.

List Ads

Lists an ad account's ads, with each ad's ad group, Pin, creative type, status and review status.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Ad

Retrieves one ad.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Ad ID. Use the List Ads template to find it.
  • See the Pinterest API reference for the response fields.

Analytics and reports​

Organic analytics for the user account and Pins need user_accounts:read, or pins:read and boards:read. Ads analytics and reports need ads:read.

Get User Account Analytics

Reads daily organic metrics for the user's account over a date range: impressions, saves, Pin clicks, outbound clicks and engagement. Each day is one record.

  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • See the Pinterest API reference for the response fields.

List Top Pins

Lists the user's top 50 Pins, ranked by a metric over a date range, with their metrics.

  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Select the metric to rank Pins by in Sort By: ENGAGEMENT, SAVE, IMPRESSION, OUTBOUND_CLICK or PIN_CLICK. Defaults to IMPRESSION.
  • See the Pinterest API reference for the response fields.

List Top Video Pins

Lists the user's top 50 video Pins, ranked by a video metric over a date range, with their metrics.

  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Select the video metric to rank Pins by in Sort By, such as IMPRESSION, SAVE, OUTBOUND_CLICK, VIDEO_MRC_VIEW, VIDEO_AVG_WATCH_TIME or VIDEO_START. Defaults to IMPRESSION.
  • See the Pinterest API reference for the response fields.

Get Pin Analytics

Reads daily metrics for one Pin over a date range. Each day is one record.

  • Enter the Pin ID. Use the List Pins or List Board Pins template to find it.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Metric Types, separated by commas, for example IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK,VIDEO_MRC_VIEW. Defaults to IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK.
  • See the Pinterest API reference for the response fields.

Get Multiple Pin Analytics

Reads metrics for up to 100 Pins over a date range. The result is one record, keyed by Pin ID.

  • Enter the Pin IDs (up to 100), separated by commas. Use the List Pins template to find them.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Metric Types, separated by commas, for example IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK,VIDEO_MRC_VIEW. Defaults to IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK.
  • See the Pinterest API reference for the response fields.

Get Ad Account Analytics

Reads ad account metrics, such as spend, impressions, clicks, CTR and conversions, by day, hour, week, month or in total.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Ad Account Targeting Analytics

Reads ad account metrics broken down by targeting type, such as age, gender, country or keyword.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Targeting Types to break the metrics down by, separated by commas, for example AGE_BUCKET,GENDER,COUNTRY,KEYWORD. Defaults to AGE_BUCKET.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Campaign Analytics

Reads metrics for one or more campaigns over a date range, such as spend, impressions, clicks and conversions.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Campaign IDs, separated by commas. Use the List Campaigns template to find them.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Campaign Targeting Analytics

Reads campaign metrics broken down by targeting type.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Campaign IDs, separated by commas. Use the List Campaigns template to find them.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Targeting Types to break the metrics down by, separated by commas, for example AGE_BUCKET,GENDER,COUNTRY,KEYWORD. Defaults to AGE_BUCKET.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Ad Group Analytics

Reads metrics for one or more ad groups over a date range.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Ad Group IDs, separated by commas. Use the List Ad Groups template to find them.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Ad Group Targeting Analytics

Reads ad group metrics broken down by targeting type.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Ad Group IDs, separated by commas. Use the List Ad Groups template to find them.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Targeting Types to break the metrics down by, separated by commas, for example AGE_BUCKET,GENDER,COUNTRY,KEYWORD. Defaults to AGE_BUCKET.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Ad Analytics

Reads metrics for one or more ads over a date range.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Ad IDs, separated by commas. Use the List Ads template to find them.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Ad Targeting Analytics

Reads ad metrics broken down by targeting type.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Ad IDs, separated by commas. Use the List Ads template to find them.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Targeting Types to break the metrics down by, separated by commas, for example AGE_BUCKET,GENDER,COUNTRY,KEYWORD. Defaults to AGE_BUCKET.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Promoted Pin Analytics

Reads metrics for the promoted Pins of a campaign over a date range.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Campaign ID. Use the List Campaigns template to find it.
  • Enter the Pin IDs, separated by commas: the pin_id values returned by the List Ads template.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Get Product Group Analytics

Reads metrics for shopping ad product groups over a date range.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Enter the Product Group IDs, separated by commas: the IDs of the product groups used in your shopping ad groups.
  • Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • See the Pinterest API reference for the response fields.

Run Ads Report

Runs an asynchronous ads report end to end and reads its rows into the Nexset: it requests a CSV report, polls until the report is FINISHED, then downloads the CSV. See Asynchronous ads reports for how it works.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Start Date in YYYY-MM-DD format (UTC). It can be up to 914 days back, and the report can cover at most 186 days. Defaults to 7 days ago.
  • Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
  • Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
  • Select the report Level: ADVERTISER, CAMPAIGN, AD_GROUP, PIN_PROMOTION, KEYWORD, PRODUCT_GROUP or PRODUCT_ITEM. Defaults to CAMPAIGN.
  • Enter the report Columns as a JSON array, for example ["SPEND_IN_DOLLAR", "IMPRESSION_1"]. Defaults to ["CAMPAIGN_NAME", "SPEND_IN_DOLLAR", "IMPRESSION_1", "CLICKTHROUGH_1", "CTR"].
  • See the Pinterest API reference for the response fields.

Get Report Status

Reads the status of an asynchronous ads report (such as IN_PROGRESS, FINISHED or FAILED), its size, and its download URL once it is finished.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Report Token: the token that Pinterest returned when the report was requested.
  • See the Pinterest API reference for the response fields.

List Report Templates

Lists the report templates saved in an ad account.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

List Delivery Metrics

Lists the definitions of Pinterest's reporting metrics, with each metric's name, definition and display name. Use it to choose report and analytics columns.

Get Metrics Ready State

Shows whether the conversion and non-conversion metrics for a day are final.

  • Enter the Date to check in YYYY-MM-DD format (UTC). Defaults to today.
  • See the Pinterest API reference for the response fields.

Audiences, customer lists and targeting​

Needs ads:read.

List Audiences

Lists an ad account's audiences, with each audience's name, type, rule, size and status.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Audience

Retrieves one audience.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Audience ID. Use the List Audiences template to find it.
  • See the Pinterest API reference for the response fields.

List Audience Insight Types

Lists the audience scopes and types available for audience insights in an ad account.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Audience Insights

Reads the demographics, interest categories and size of your total audience, your engaged audience, or the total Pinterest audience.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Select the Insight Type: YOUR_TOTAL_AUDIENCE, YOUR_ENGAGED_AUDIENCE or PINTEREST_TOTAL_AUDIENCE. Defaults to YOUR_TOTAL_AUDIENCE.
  • See the Pinterest API reference for the response fields.

List Customer Lists

Lists an ad account's customer lists, with each list's name, status and record counts.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Customer List

Retrieves one customer list.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Customer List ID. Use the List Customer Lists template to find it.
  • See the Pinterest API reference for the response fields.

List Targeting Templates

Lists the targeting templates saved in an ad account.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the response fields.

Get Targeting Options

Lists the values for one targeting type, such as interests, locations, age buckets, genders or app types.

  • Select the Targeting Type, such as INTEREST, LOCATION, GEO, AGE_BUCKET, GENDER, LOCALE, APPTYPE or KEYWORD. Defaults to INTEREST.
  • See the Pinterest API reference for the response fields.

Get Interest Targeting Option

Retrieves one interest with its level and child interests.

  • Enter the Interest ID. Use the Get Targeting Options template with Targeting Type set to INTEREST to find it.
  • See the Pinterest API reference for the response fields.

Keywords​

Ad group keywords and keyword metrics need ads:read; trending keywords need user_accounts:read.

List Keywords

Lists the keywords of an ad group, with each keyword's value, match type, bid and archived flag.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Ad Group ID. Use the List Ad Groups template to find it.
  • See the Pinterest API reference for the response fields.

Get Keyword Metrics

Reads the monthly search volume range for keywords in a country.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the two-letter Country Code (ISO 3166-1 alpha-2). Defaults to US.
  • Enter the Keywords, separated by commas.
  • See the Pinterest API reference for the response fields.

List Trending Keywords

Lists the top trending search keywords for a region: growing, monthly, yearly or seasonal.

  • Select the Region, such as US, CA, GB+IE or DE+AT+CH. Defaults to US.
  • Select the Trend Type, which sets how keywords are ranked: growing, monthly, yearly or seasonal. Defaults to growing.
  • See the Pinterest API reference for the response fields.

Catalogs​

Needs catalogs:read. Reading the product Pins of a product group also needs pins:read and boards:read.

List Catalogs

Lists the user's catalogs, with each catalog's ID, name and type.

List Catalog Feeds

Lists the product data feeds, with each feed's name, format, location, schedule and status.

Get Catalog Feed

Retrieves one product data feed.

  • Enter the Feed ID. Use the List Catalog Feeds template to find it.
  • See the Pinterest API reference for the response fields.

List Feed Processing Results

Lists the ingestion runs of a feed, with item counts, errors and warnings for each run.

  • Enter the Feed ID. Use the List Catalog Feeds template to find it.
  • See the Pinterest API reference for the response fields.

List Catalog Item Issues

Lists the item-level validation issues of one feed processing result.

  • Enter the Processing Result ID. Use the List Feed Processing Results template to find it.
  • See the Pinterest API reference for the response fields.

List Catalog Product Groups

Lists the catalog product groups (filters over a feed), with each group's name, filters and status.

Get Catalog Product Group

Retrieves one catalog product group.

  • Enter the Product Group ID. Use the List Catalog Product Groups template to find it.
  • See the Pinterest API reference for the response fields.

Get Product Group Counts

Reads the product counts of a product group: total, in stock, out of stock and preorder.

  • Enter the Product Group ID. Use the List Catalog Product Groups template to find it.
  • See the Pinterest API reference for the response fields.

List Product Group Products

Lists the product Pins in a catalog product group.

  • Enter the Product Group ID. Use the List Catalog Product Groups template to find it.
  • See the Pinterest API reference for the response fields.

Get Catalog Items

Reads catalog items by item ID for a country and language. This template sends a POST request, but it only reads data.

  • Enter the Items Request: the JSON request body, with country, language and filters (catalog_type and item_ids). The default, {"country": "US", "language": "EN", "filters": {"catalog_type": "RETAIL", "item_ids": ["SKU1"]}}, is an example; replace the item IDs with your own.
  • See the Pinterest API reference for the response fields.

Get Items Batch Status

Reads the status and per-item results of a catalog items batch.

  • Enter the Batch ID: the batch_id value returned by the Batch Catalog Items destination.
  • See the Pinterest API reference for the response fields.

Terms​

Keyword research terms. Needs ads:read.

List Related Terms

Lists terms related to the input terms, for keyword research.

List Suggested Terms

Lists popular search terms that start with the input term.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Asynchronous ads reports​

Pinterest builds ads reports asynchronously: you request a report, Pinterest generates it in the background, and you download the file once it is ready. The connector supports this in two ways:

  • Run Ads Report does the whole process in one source. On each run, it:

    1. requests a CSV report for the ad account, with the level, columns, granularity and date range from the template settings, and gets back the report's token;
    2. polls the report's status with that token until report_status is FINISHED, and stops with an error if Pinterest reports FAILED;
    3. downloads the CSV from the report's url, a pre-signed link that needs no Pinterest token, and reads each row of the CSV as a record.
  • Get Report Status reads the status, size and download url of a report you requested in another way, such as through the Pinterest API directly, given its token. There is no destination template that requests a report on its own.

A report can start up to 914 days back and cover at most 186 days. For metrics as JSON, without a report, use the analytics templates above, such as Get Campaign Analytics, which read at most 90 days back. Use Get Metrics Ready State to check whether a day's metrics are final before you read them.

Manual configuration​

Pinterest data sources can also be manually configured to ingest data from any valid Pinterest API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or optional filters that the templates do not send. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. Pinterest endpoint URLs take the form https://api.pinterest.com/v5/.... List endpoints return their records in items and the next page's cursor in bookmark. See the Pinterest API reference for the available endpoints.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Pinterest data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Pinterest destination, and select the Send to Destination option from the menu. Select the Pinterest API connector from the list of available destination connectors, then select the credential that will be used to connect to Pinterest, and click Next; or, create a new Pinterest API credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Pinterest API endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Each record in the Nexset is sent as the JSON body of one request, one record at a time, so shape each record to match the request body that Pinterest documents for the endpoint. The campaign, ad group and ad templates are the exception: they send records in batches of up to 30, because Pinterest creates and updates these objects in bulk. ID settings, such as an ad account or board ID, are fixed on the destination and apply to every record it sends. Templates are marked Publishes content, Spends budget or Deletes data as described in Prerequisites.

The ads and catalog templates need the ads:write or catalogs:write scope, which Pinterest must approve for your app, and which you must add to the credential's Access Scope before you authorize it.

Boards​

Needs boards:read and boards:write, which are in the default scope.

Create Board

Creates a board from each record. A record carries name and, optionally, description and privacy.

  • Publishes content: boards are public unless privacy is SECRET, so a new board can appear on the user's public profile.
  • See the Pinterest API reference for the request body fields.

Update Board

Updates a board. A record carries the fields to change, such as name, description or privacy.

  • Publishes content: changes to a public board appear on the user's public profile.
  • Enter the Board ID. Use the List Boards template to find it.
  • See the Pinterest API reference for the request body fields.

Delete Board

Deletes a board.

  • Deletes data: permanently deletes the board and its Pins.
  • The record's content is not sent; each record repeats the same request, so send a single record.
  • Enter the Board ID. Use the List Boards template to find it.
  • See the Pinterest API reference for details.

Board sections​

Needs boards:read and boards:write, which are in the default scope.

Create Board Section

Adds a section to a board. A record carries name.

  • Publishes content: the new section appears on the board, on the user's public profile.
  • Enter the Board ID. Use the List Boards template to find it.
  • See the Pinterest API reference for the request body fields.

Update Board Section

Renames a board section. A record carries name.

  • Publishes content: the change appears on the board, on the user's public profile.
  • Enter the Board ID. Use the List Boards template to find it.
  • Enter the Section ID. Use the List Board Sections template to find it.
  • See the Pinterest API reference for the request body fields.

Delete Board Section

Deletes a board section.

  • Deletes data: permanently deletes the section and the Pins in it.
  • The record's content is not sent; each record repeats the same request, so send a single record.
  • Enter the Board ID. Use the List Boards template to find it.
  • Enter the Section ID. Use the List Board Sections template to find it.
  • See the Pinterest API reference for details.

Pins​

Needs pins:read, pins:write, boards:read and boards:write, which are in the default scope.

Create Pin

Creates a Pin from each record. A record carries board_id, media_source (for example, source_type set to image_url, and url) and, optionally, title, description and link.

  • Publishes content: the Pin is published to the user's profile, and is public on a public board.
  • See the Pinterest API reference for the request body fields.

Update Pin

Updates a Pin. A record carries the fields to change, such as title, description, link, alt_text or board_id.

  • Publishes content: the changes appear on the published Pin.
  • Enter the Pin ID. Use the List Pins or List Board Pins template to find it.
  • See the Pinterest API reference for the request body fields.

Save Pin

Saves an existing Pin to one of the user's boards. A record carries board_id and, optionally, board_section_id.

  • Publishes content: the saved Pin appears on the board, on the user's public profile.
  • Enter the Pin ID. Use the List Pins or List Board Pins template to find it.
  • See the Pinterest API reference for the request body fields.

Delete Pin

Deletes a Pin.

  • Deletes data: permanently deletes the Pin.
  • The record's content is not sent; each record repeats the same request, so send a single record.
  • Enter the Pin ID. Use the List Pins or List Board Pins template to find it.
  • See the Pinterest API reference for details.

Ad accounts and conversions​

Needs ads:write, which is not in the default scope. See Prerequisites.

Create Ad Account

Creates an ad account from each record. A record carries name, owner_user_id, country, currency and time_zone.

Create Conversion Tag

Creates a conversion tag, and returns its code snippet. A record carries name and, optionally, settings such as aem_enabled.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Send Conversion Events

Sends conversion events to the Pinterest Conversions API, for ad attribution. A record carries data: a list of events, each with event_name, action_source, event_time, event_id and user_data.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Campaigns​

Needs ads:write, which is not in the default scope. See Prerequisites.

Create Campaign

Creates campaigns. A record carries ad_account_id, name, objective_type, and, optionally, status, budgets and dates. A campaign is created ACTIVE unless the record sets status.

  • Spends budget: a new campaign is ACTIVE unless the record sets status, and its ad groups and ads can start delivering and spending budget.
  • Records are sent in batches of up to 30, as a JSON array in one request, so shape each record as one object of that array.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Update Campaign

Updates campaigns. A record carries the campaign's id, ad_account_id, and the fields to change, such as status, budgets or dates.

  • Spends budget: setting status to ACTIVE or raising a budget resumes or increases spending.
  • Records are sent in batches of up to 30, as a JSON array in one request, so shape each record as one object of that array.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Ad groups​

Needs ads:write, which is not in the default scope. See Prerequisites.

Create Ad Group

Creates ad groups with a budget, bid and targeting. A record carries campaign_id, name, billable_event and the other ad group settings.

  • Spends budget: an ad group in an active campaign can start delivering and spending budget.
  • Records are sent in batches of up to 30, as a JSON array in one request, so shape each record as one object of that array.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Update Ad Group

Updates ad groups. A record carries the ad group's id and the fields to change, such as status, budget, bid or targeting.

  • Spends budget: changes take effect on live ad groups, and turning delivery on resumes spending.
  • Records are sent in batches of up to 30, as a JSON array in one request, so shape each record as one object of that array.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Ads​

Needs ads:write, which is not in the default scope. See Prerequisites.

Create Ad

Promotes Pins as ads. A record carries ad_group_id, pin_id, creative_type and, optionally, status.

  • Spends budget: an ad in an active ad group can start delivering and spending budget.
  • Records are sent in batches of up to 30, as a JSON array in one request, so shape each record as one object of that array.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Update Ad

Updates ads. A record carries the ad's id and the fields to change, such as status.

  • Spends budget: changes take effect on live ads, and turning delivery on resumes spending.
  • Records are sent in batches of up to 30, as a JSON array in one request, so shape each record as one object of that array.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Audiences, customer lists and targeting​

Needs ads:write, which is not in the default scope. See Prerequisites.

Create Audience

Creates an audience (visitor, engagement or actalike). A record carries ad_account_id, name, rule and audience_type.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Update Audience

Updates an audience. A record carries ad_account_id and the fields to change, such as name, description or rule.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Audience ID. Use the List Audiences template to find it.
  • See the Pinterest API reference for the request body fields.

Create Customer List

Creates a customer list from hashed emails or mobile advertising IDs. A record carries name, records and list_type.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Update Customer List

Adds records to or removes records from a customer list. A record carries operation_type (ADD or REMOVE) and records.

  • Deletes data: a REMOVE operation removes users from the list, and from the audiences built on it.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • Enter the Customer List ID. Use the List Customer Lists template to find it.
  • See the Pinterest API reference for the request body fields.

Create Targeting Template

Saves a targeting template. A record carries name and targeting_attributes.

  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Keywords​

Needs ads:write, which is not in the default scope. See Prerequisites.

Create Keywords

Adds keywords to an ad group or campaign. A record carries parent_id and keywords, a list of objects with value and match_type.

  • Spends budget: keywords added to a live ad group or campaign can start delivery and spending.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Update Keywords

Changes keyword bids or archives keywords. A record carries keywords, a list of objects with id and the fields to change, such as bid or archived.

  • Spends budget: bid changes take effect on live keywords, and can increase spending.
  • Enter the Ad Account ID. Use the List Ad Accounts template to find it.
  • See the Pinterest API reference for the request body fields.

Catalogs​

Needs catalogs:write, which is not in the default scope, and catalogs:read. See Prerequisites.

Create Catalog

Creates a catalog. A record carries name and catalog_type.

Create Catalog Feed

Creates a product data feed, whose items become product Pins. A record carries name, format, location, default_currency and the other feed settings.

  • Publishes content: the feed's items become product Pins on the user's profile.
  • See the Pinterest API reference for the request body fields.

Update Catalog Feed

Updates a product data feed. A record carries the fields to change.

  • Publishes content: the changes are applied to the product Pins built from the feed.
  • Enter the Feed ID. Use the List Catalog Feeds template to find it.
  • See the Pinterest API reference for the request body fields.

Ingest Catalog Feed

Starts an ingestion of a product data feed now, which creates or updates its product Pins.

  • Publishes content: creates or updates the product Pins built from the feed.
  • The record's content is not sent; each record repeats the same request, so send a single record.
  • Enter the Feed ID. Use the List Catalog Feeds template to find it.
  • See the Pinterest API reference for details.

Delete Catalog Feed

Deletes a product data feed.

  • Deletes data: deletes the feed and its product Pins.
  • The record's content is not sent; each record repeats the same request, so send a single record.
  • Enter the Feed ID. Use the List Catalog Feeds template to find it.
  • See the Pinterest API reference for details.

Create Catalog Product Group

Creates a product group (a filter over a feed) for shopping ads. A record carries name, feed_id and filters.

Update Catalog Product Group

Updates a product group. A record carries the fields to change, such as name, filters or is_featured.

  • Enter the Product Group ID. Use the List Catalog Product Groups template to find it.
  • See the Pinterest API reference for the request body fields.

Delete Catalog Product Group

Deletes a catalog product group.

  • Deletes data: deletes the product group.
  • The record's content is not sent; each record repeats the same request, so send a single record.
  • Enter the Product Group ID. Use the List Catalog Product Groups template to find it.
  • See the Pinterest API reference for details.

Batch Catalog Items

Creates, updates or deletes catalog items in one batch request. A record carries country, language, operation and items. Read the batch's results with the Get Items Batch Status source.

  • Publishes content: created and updated items become product Pins on the user's profile.
  • Deletes data: a DELETE operation removes the items and their product Pins.
  • See the Pinterest API reference for the request body fields.

Manual configuration​

Pinterest destinations can also be manually configured to send data to any valid Pinterest API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

The Pinterest API expects JSON request bodies for create and update requests. Include the ad account, board and other object IDs in the endpoint URL, for example https://api.pinterest.com/v5/ad_accounts/AD_ACCOUNT_ID/campaigns. Campaign, ad group and ad requests take a JSON array of up to 30 objects.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Pinterest endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Pinterest endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.