Get Pin Analytics
Pin-level analytics (impressions, saves, clicks, outbound clicks) over a date range.
PinBridge copies every published pin's analytics nightly, so most reads are answered from that stored history (source: stored in the response, with data_as_of) without calling Pinterest. Live ranges are capped at 90 days, stored ranges at 366. Sandbox-simulated pins return zeroed metrics.
A pin deleted on Pinterest (removed_from_pinterest_at set) is answered from the stored history. Without stored history it fails with 409 pin_removed_on_pinterest, which is also what a live read returns when Pinterest no longer has the pin.
Request
- Base URL: https://api.pinbridge.io (the document declares no server; this is the origin it was published from)
- URL: https://api.pinbridge.io/v1/pins/{pin_id}/analytics
- Auth: one of:
- API key in header X-API-Key
- HTTP bearer
Path parameters
Query parameters
Inclusive start (YYYY-MM-DD); default 30 days ago
Inclusive end (YYYY-MM-DD); default today
Comma-separated Pinterest metric types, e.g. IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK. Defaults to the organic engagement set.
auto (default): PinBridge's stored history when it covers the range, else Pinterest. stored: stored history only (up to 366 days, beyond Pinterest's 90). live: always ask Pinterest (counts against the read limit).
false: return only the range totals, with an empty daily list. Use it when the totals are all you need, e.g. over 90 days.
Headers
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.