AmazonAmazon StorefrontAmazon InfluencerAffiliate MarketingAPI Guide

Amazon Storefront API: Read Creator Shops, Idea Lists and Trending Picks

Read an Amazon creator storefront with one API call: profile, linked socials, idea lists with item counts, curated posts and trending picks with prices, for 0.5 credits.

SocQUpdated November 19, 20265 min read

Creators in the Amazon Influencer Program run a storefront at amazon.com/shop/<name>. They group products into idea lists and curated posts, link their social accounts, and highlight trending picks. For an affiliate or influencer team, that page answers practical questions: who the creator is, where else they post, what they recommend this season, and how big each list is.

On 2026-11-17 SocQ added the Amazon Storefront API, which returns one storefront as a single structured record. This guide covers the request, the fields, the price and how to fit it into a creator-research workflow.

Quick answer: Send one storefront URL in url to POST /v1/amazon/shop. Poll GET /v1/tasks/{task_id} until the task succeeds, then read one row from data.results.items with the creator profile, social_urls, lists, curations and trending_picks. Each request costs 0.5 credits ($0.0025).

What the Endpoint Returns

1 SocQ credit = $0.005.

EndpointWhat it returnsPrice
Amazon Storefront APIOne row per storefront: creator name, description, avatar, top-creator flag, linked social profiles, idea lists with item counts, curated posts with product counts, and trending picks with prices0.5 credits ($0.0025) per call

The row covers the first page of the storefront's lists, curations and trending picks. A storefront that does not exist fails with a refund, so you are not charged for dead URLs.

Authentication and the Async Task Flow

All SocQ requests authenticate with an API key, and the same header is used for submit, task status and result requests:

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Every collection runs as a background task:

submit -> task_id -> queued -> running -> succeeded
                                   \-> failed

The submit response contains data.task_id and data.status. Poll the task with that ID:

curl "https://api.socq.ai/v1/tasks/$TASK_ID?limit=50" \
  -H "Authorization: Bearer $SOCQ_API_KEY"

When status is succeeded, the response includes the first page of normalized records in data.results.items. limit defaults to 50 and goes up to 500; if has_more is true, pass results.next_cursor as cursor. While a task is queued, running or failed, the endpoint returns task metadata without results.

An optional callback_url in the submit body makes SocQ send one POST with a task summary when the task finishes; read the records with GET /v1/tasks/{task_id}. A client-side timeout does not cancel a task, so resume with the same task ID instead of paying for a duplicate. 402 means insufficient credits; 429 means the key hit a rate or credit limit.

Request a Storefront

The only input is url, one storefront in the form amazon.com/shop/<name>. Other Amazon marketplaces work the same way.

curl -X POST "https://api.socq.ai/v1/amazon/shop" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://www.amazon.com/shop/sydneydelrey"
  }'

The endpoint takes one URL per request. To read a list of storefronts, submit one task per URL, store each task_id with its input, and poll them independently.

Understand the Storefront Record

A trimmed result from the documentation example looks like this:

{
  "id": "sydneydelrey",
  "platform": "amazon",
  "resource": "shop",
  "type": "storefront",
  "url": "https://www.amazon.com/shop/sydneydelrey",
  "name": "sydney del rey",
  "is_top_creator": true,
  "social_urls": [
    "https://vm.tiktok.com/ZTFrowSpg/",
    "https://www.youtube.com/channel/UCWvW1JOQ-nsAinO1jLFgrVA",
    "https://www.pinterest.com/sydneydelrey"
  ],
  "lists": [
    {
      "title": "Holiday home goods",
      "url": "https://www.amazon.com/shop/sydneydelrey/list/XYAIGEFWJGML?tag=sydneybertonc-20",
      "items_count": 107
    }
  ],
  "curations": [
    {
      "title": "f/w fit try ons",
      "url": "https://www.amazon.com/shop/sydneydelrey/curation/71fad634-5787-4ee1-bc3c-6e3ca23e5eae",
      "posts_count": 109
    }
  ],
  "trending_picks": [
    {
      "url": "https://www.amazon.com/shop/sydneydelrey/getProductDetails/B0FCLQD6BN?showRelatedPost=true&tag_override=sydneybertonc-20",
      "price": 24.99,
      "discount": null
    }
  ]
}

The fields, grouped by what you would use them for:

  • Creator identity: id (the storefront name from the URL), name, text (the description the creator wrote), avatar_url and is_top_creator, which shows whether Amazon marks the creator as a top creator.
  • Cross-platform reach: social_urls, the social profiles linked on the storefront.
  • Catalog structure: lists with title, url, image_url and items_count; curations with title, url, image_url and posts_count (the number of products in the curated post).
  • Current promotions: trending_picks with url, image_url, price in the marketplace's currency and discount when one is shown.

Every row also carries collected_at, the time SocQ collected it. Prices change, so store that timestamp with any price you keep. The full field table is in the Amazon Storefront docs.

When to Use It

Scouting affiliate partners. is_top_creator, the number of lists and the items_count on each give a quick sense of how active a storefront is before anyone on your team opens it.

Following what a creator recommends. Re-read a storefront on a schedule and compare list titles, counts and trending picks between runs to see what the creator is pushing this season.

Connecting a storefront to the creator's social accounts. social_urls gives you the TikTok, YouTube or Pinterest profiles the creator links. Feed those into the Creator APIs to find public business emails, or into the platform profile endpoints for follower counts.

Product research. Trending picks point to products. To get full product data, reviews or category rankings, use SocQ's other Amazon endpoints, such as the Amazon Product Details API and the Amazon Best Sellers API. For an overview of how these compare with Amazon's own APIs, see Amazon Product Advertising API alternatives.

Production Tips

  1. Normalize URLs. Keep one canonical amazon.com/shop/<name> form per creator so you do not pay twice for the same storefront.
  2. Expect a first-page snapshot. Lists, curations and trending picks are the ones shown on the storefront's first page. Treat counts as a snapshot at collected_at.
  3. Handle failures separately. A storefront that does not exist fails with a refund. Mark it as gone rather than retrying it.
  4. Budget simply. At 0.5 credits per storefront, 1,000 storefronts cost 500 credits, or $2.50.

FAQ

What is the Amazon Storefront API?

It is a SocQ endpoint that reads one Amazon creator storefront (amazon.com/shop/<name>) and returns the creator profile, linked socials, idea lists, curated posts and trending picks as one structured record.

Does it work outside amazon.com?

Yes. The documentation says other Amazon marketplaces work the same way: send the storefront URL on that marketplace in url. Prices in trending_picks are in that marketplace's currency.

Does it return every product in every list?

No. The row covers the first page of the storefront: each list's title, URL, cover image and items_count, each curated post's product count, and the current trending picks. It does not expand every list item.

Am I charged if the storefront does not exist?

No. A storefront that does not exist fails with a refund. A successful request costs 0.5 credits ($0.0025).

Can I send several storefronts in one request?

The request takes a single url. Submit one task per storefront and track each task_id.

AMAZON API

Test the workflow with a public Amazon URL

Submit public inputs and receive normalized records with traceable source context.

Explore Amazon APIs