Pinterest Profiles
Pinterest profiles are public account pages with usernames, display names, bios, profile images, linked websites, and visible follower, following, board, and saved counts. These identity fields and account signals support profile enrichment, public account comparison, and time-based monitoring.
Features
- Public profile URL scopeProcess one or more supported Pinterest profile URLs while excluding Pin links, short links, search pages, and other non-profile paths.
- Profile identity and presentationReturn the profile ID, canonical URL, username, display name, bio, profile image, and linked website in one normalized record.
- Visible account countsKeep available follower, following, board, and saved counts as separate metrics for account-level comparison.
- Collection and source contextAttach collected_at plus available country code, created-Pins page URL, source update value, and discovery input without mixing them into identity fields.
Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | Required list of public Pinterest profile URLs. Each URL must use HTTP or HTTPS on a Pinterest domain and contain one non-reserved username path segment. |
How to Use
Submit known public profile URLs, track the asynchronous task, and read normalized profile records with cursor pagination.
- Prepare one or more public Pinterest profile URLs whose path contains a single username segment.
- Submit the links as urls to /v1/pinterest/profiles and capture task_id.
- Poll /v1/tasks/{task_id} until processing succeeds or returns a failure.
- Read data.results.items, then request the next page with next_cursor while has_more is true.
curl -X POST "https://api.socq.ai/v1/pinterest/profiles" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://www.pinterest.com/example/"]}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueBest Use Cases
- Public profile enrichment: Add username, display name, bio, profile image, website, and country context to records connected to known profile URLs.
- Account footprint comparison: Compare visible follower, following, board, and saved counts across a selected set of public profiles.
- Public profile monitoring: Store identity fields and visible metrics with collected_at to compare profile presentation and account signals across collection times.
Pro Tips
- Use a full HTTP or HTTPS Pinterest profile URL with one username path segment; pin.it, /pin/, /search/, and other reserved paths are rejected.
- Normalize submitted URLs and deduplicate returned profiles by id when available, using url as the fallback stable key.
- Treat bio, image, website, country code, source update value, created-Pins page URL, and individual metrics as optional fields.
- Keep collected_at beside visible account counts so later runs remain distinguishable as separate public snapshots.
- Use Pinterest User Pins API when you need Pin records from a profile; this endpoint returns profile metadata and counts rather than boards, Pins, or audience lists.
Related APIs
Use these APIs when you need a different type of public Pinterest data.
- Pinterest Pins API — Resolve public Pin URLs into normalized content, creator, media, taxonomy, timestamps, and visible metrics.
- Pinterest User Pins API — Discover public Pins from profile URLs with a per-profile limit, normalized content, creator, media, timestamps, and visible metrics.
- Pinterest Search API — Search public Pins by text query with a result limit, returning normalized content, creator, media, taxonomy, timestamps, and visible metrics.