Pinterest User Pins API: Public Pin Images and Links

Retrieve the available public pin records for the account identified by the required string query parameter username. The parameter documentation permits a Pinterest username or account ID, but the recorded probe verified only a username. The default example_user is an illustrative value; replace it with the intended account. No pagination parameter is exposed. Observed response: a successful request for marthastewart returned HTTP 200 with status set to ok, request_id, message set to null and data.pins containing 25 records. The probe confirmed pin IDs, public board URLs, the account's pinner identity, images and outbound links. This is evidence of a returned collection, not a fixed page size or a complete account export. Additional documented fields, not individually confirmed by the probe metadata: each pin may include id, title, description, description_html, alt_text, created_at, domain, link, seo_title and seo_url; board contains id and name, pinner contains id and username, and images may contain a size-keyed entry such as images["236x"].url. The source example also includes comment_count, repin_count, reaction_counts.like, comments, grid_title, grid_description, dominant_color and flags such as is_video, is_repin, is_promoted and privacy. Treat these example fields as optional rather than a guaranteed record schema, preserve IDs as strings and handle absent text, images or links. Counts, where present, are record attributes rather than engagement history. The documentation also illustrates HTTP 400 with a detail string, HTTP 422 with detail entries containing loc, msg and type, and HTTP 500 with status, request_id and data.pins. These are unverified error examples, not observed failures or guaranteed error formats. Use returned source references for attribution and compare pinner identities before assigning authorship. An account's collection may contain saved content; neither inclusion nor a media URL grants ownership or reuse rights. This route does not expose pagination, private boards, restricted pins or deleted content, and its available collection must not be described as every pin associated with the account.

API Features

Account-scoped public pin collection Provide the required username query input to retrieve the available pins for a selected account; the recorded username request returned 25 pin records.

Source-linked editorial records Observed pin IDs, public board references, images and outbound links support review sheets that retain the connection to original content.

Pinner-aware attribution checks Compare returned pinner identities before assigning authorship, since saved pins and linked media do not establish that the selected account created every item.

Partial-snapshot boundaries Deduplicate returned pin IDs across timestamped runs while keeping the collection explicitly partial: no page or cursor input is documented.

Live API Demo

GET /api/project/pinterest-scraper/list-user-pins

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/pinterest-scraper/list-user-pins?key=<API_KEY>&username=example_user'

curl -X GET 'https://api.opendata-api.com/api/project/pinterest-scraper/list-user-pins?key=<API_KEY>&username=example_user'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Create an editorial review sheet for a chosen account using available pin IDs, image links and source references while recording content-rights review separately.
Build an outbound-domain inventory from returned pin links to study where an account's available content directs readers or shoppers.
Store timestamped, deduplicated pin snapshots to flag newly observed IDs without interpreting a missing ID as proof of deletion.
Compare each returned pinner identity with the selected account before classifying a pin as account-associated content rather than making an unsupported authorship claim.

Frequently asked questions

Should I pass a username or a numeric user ID to /pins?

The required query parameter is named username. Its documentation mentions a username or account ID, but only a username was verified by the recorded probe. Prefer the intended account's username when available; numeric-ID behavior has not been confirmed. Replace the illustrative example_user default.

Will this return all pins or let me request the next page?

No pagination input is documented. The successful probe returned 25 pins, but that does not establish a guaranteed page size or complete history. Treat the result as the available public collection, not an exhaustive export.

Which pin response details were actually observed?

The recorded HTTP 200 response had status, request_id, message set to null and data.pins. Its 25 records included pin IDs, public board URLs, pinner identity, images and outbound links. Other documented fields, including text, counts and content flags, were not individually confirmed by the probe metadata and should be handled as optional.

Do image URLs and pinner information prove media ownership?

No. Public collections can include saved content, and neither a pinner identity nor an image URL grants ownership or reuse rights. Retain source references and verify attribution and rights separately before reuse.

How should I store pin IDs and compare repeated results?

Preserve pin IDs as strings, record when each snapshot was collected and deduplicate by ID. Newly observed IDs can support change review, but absence from a later partial collection does not prove that a pin was deleted.

Related operations

Guides

View Subscription Plans →

List an account's available public pins