# Pinterest Board API (https://www.socialcrawl.dev/platforms/pinterest/board)

> Returns pins from a Pinterest board, up to 15 per page. Each pin includes its text (title, or description when the title is empty), image URL, author, and save, comment and share counts; many pins have no title or description, so the text can be null. A board page does not carry the date a pin was created, so `post.published_at` is null on a plain call, and `post.engagement.likes` (reactions) is null on pins that have no reactions. `include=engagement` joins each row, in the same call, to the per-pin lookup: the creation date lands on the row and `likes` is filled from the pin (0 when it has no reactions); counts the board already carried are kept. As of 19/10/2026 Pinterest serves board pins with an encrypted pin id (`post.url` reads `/pin/e1_...`, 15 of 15 pins on the board measured), which the per-pin lookup cannot read: such a row keeps its nulls and is refunded, and the response says so in `_warnings` (`engagement_unavailable` when no row was filled, `engagement_partial` when some were). Cost: 1 credit for the page plus 1 credit per row filled from a fresh lookup (15 rows max, so 16 credits at most); rows already in cache are filled for free, rows that could not be filled are refunded, and a repeat of the same call within the cache window is 0 credits. Time: a plain call is usually about 5 seconds; `include=engagement` adds 4 to 10 seconds on a fresh page (the lookups run in parallel and the call waits for the slowest, never more than 12 seconds). `limit=N` caps the rows and the credits together. The response carries a `hydration` block itemising rows, lookups, cache hits, credits and milliseconds. Send `pagination.next_cursor` back as `cursor` to walk the rest of the board, with or without `include`; `has_more` goes false on the last page.

TL;DR: `GET /v1/pinterest/board` costs 1 credit for the page. include=engagement holds 1 credit per row, at most 15 (or `limit`), and keeps only the rows filled from a fresh lookup, so a page is at most 16 credits; rows served from cache are free, unfilled rows are refunded, and a repeat of the same call within the cache window costs 0. With `max_pages`, `max_items` or `max_credits`, each page walked is billed at this price (a cached page is free), and `max_credits` caps the total. and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | Full URL of the Pinterest board |
| `trim` | no | Set to true for a trimmed down version of the response |
| `cursor` | no | Cursor to get the next page of pins. Take it from `pagination.next_cursor` on the previous response. |
| `include` | no | Set to `engagement` (one token only) to fill `post.published_at` and `post.engagement.likes` (plus any save, comment or share count the board row lacked) in this one call on every row the per-pin lookup can read. A row whose `post.url` is an encrypted `/pin/e1_...` link (every pin measured on 19/10/2026) cannot be read: it stays as it was, is refunded, and `_warnings` carries `engagement_unavailable` or `engagement_partial`. Holds 1 credit per row (at most 15, or `limit`) and keeps only the rows filled from a fresh lookup; rows already in cache and rows that could not be filled are refunded, so the most a call can cost is 1 + rows. Adds 4 to 10 seconds on a fresh page (never more than 12) and nothing when the rows are already cached; read `data.hydration` for the rows, the credits held and kept, and the time. (engagement) |
| `limit` | no | Take the top N pins of the page (1 to 15). With `include=engagement` it also caps the extra credits at N: `limit=4&include=engagement` costs at most 5. It is not a page size: `next_cursor` still advances past the full page, so pins beyond N on this page are not returned by the next page. |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/pinterest/board" \
  --data-urlencode "url=https://www.pinterest.com/lizmrodgers/moms-night/" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I scrape a Pinterest board's pins with an API?

Send a GET request to /v1/pinterest/board with the full board URL in the url parameter. SocialCrawl returns every pin on the board with its text, image URL, save count, and comment count, paginated with a cursor. Board rows carry no date; include=engagement fills each pin's date at 1 extra credit per row filled.

### How do I paginate through a large Pinterest board?

Pass the cursor parameter returned in the previous response to fetch the next page. Loop until the response has no cursor. This is the standard pattern for exhausting boards with thousands of pins.

### What data does each board pin include?

Each pin returns id, permalink, text, image URL at multiple resolutions, save count, comment and share counts, and author info. All fields land in the unified SocialCrawl post schema, identical to the pin endpoint.

### Can I trim the board response for lean JSON?

Yes. Pass trim=true and the endpoint returns a compact payload. Useful when you need just the pin IDs and image URLs, for example, building a visual grid or archiving a board to your own storage.

### How much does the Pinterest Board API cost?

Each page of board pins costs 1 credit on the standard tier. New accounts get 100 free credits with no credit card required, enough to paginate through about 100 pages of board pins before paying anything.

See the full Pinterest API: https://www.socialcrawl.dev/platforms/pinterest

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to scrape a Pinterest board's pins with an API
- What does the SocialCrawl Pinterest Board endpoint return?