Stan Store API. Creator stores as JSON.
Creator profiles, every listed product, booking availability and the creator directory, returned in one typed contract. Name a handle and get JSON.
- Creator profiles
- Products + booking
- 1 credit per request
- Failed requests aren't charged
Teams running monitoring, research, and enrichment pipelines
Why Social Fetch
Stan Store data as JSON. You build the product.
Live Stan Store data in one response shape, with platform changes handled for you.
Stan Store, plus every other platform
One key and one response envelope for Stan Store and 56 more platforms.
Pricing you can reason about
One request, one credit. Know how far your balance will go before you run your next batch.
Live data on every request
Fetch public data when you ask for it.
Nothing to maintain
We handle platform changes and breakages.
Built for production jobs
Run concurrent workloads with explicit statuses and request IDs.
Regular jobs. Better rates.
Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.
What Stan Store data can you get?
5 endpoints, one API key. Every response comes back as live JSON in the same envelope.
Creators
Products
Availability
Browse all 5 Stan Store endpoints
What teams build with Stan Store data
Monitoring, enrichment, research and content workflows on Stan Store data, on the same API as every other platform.
How it works
Your first request in three steps.
Use TypeScript or your automation tool of choice.
Sources
+ 51 more platforms
One request
GET/v1/tiktok/profiles/
x-api-key: sk_live_••••••••
Same JSON shape
{
"data": {
"lookupStatus": "found",
"profile": {
"platform": "tiktok",
"handle": "charlidamelio",
"displayName": "charli d’amelio",
"verified": true
},
"metrics": {
"followers": 160263648
}
}
}Step 1
Create your free account
Get an API key with 100 requests included.
Step 2
Choose an endpoint
Pass a username, URL, keyword, or post ID.
Step 3
Get clean JSON
Use the response immediately or send it into your pipeline.
Works with your stack
Code, automate, or connect your AI.
TypeScript
n8n
- Make
- Apify
- MCP
- AI clients
Pricing
Social data, priced simply.
Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.
Starter
18,000credits
$1.61 per 1k · $0.00161 per request
- Top up from $1.61 / 1k if you run out
- Up to 25 monitors
Growth
50,000credits
$1.58 per 1k · $0.00158 per request
- Top up from $1.58 / 1k if you run out
- 5 team seats
- Up to 100 monitors
Scale
150,000credits
$1.50 per 1k · $0.00150 per request
- Top up from $1.50 / 1k if you run out
- 25 team seats
- Up to 250 monitors
- Cancel anytime
- 30-day money-back guarantee
- Price locked while you stay
Need 1M+ credits, invoicing, or volume rates? Talk to us
Trust signals
DevHunt
Product Hunt
Uneed
Customers
Teams building on Social Fetch.
“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”
“Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”
“Live profile data on every request. We never flag accounts from a stale cache.”
“Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”
Stan Store API: common questions
What can I get from a Stan Store creator?
Call GET /v1/stan-store/creators/{handle}. A found response carries profile (handle, displayName, bio, avatarUrl, profileUrl, verified), socials, paymentMethods, language, currency, termsText, storeId, storeName, sections and products. The products array is every page the creator lists, in store order.
How do I look up one product?
Use GET /v1/stan-store/creators/{handle}/products/{slug}. The slug is the last path segment of the product page, for example the-financial-selfcare-experience--audio-series. On found, data.product carries the full record including price, inventory, questions, reviews, course, meeting, webinar, upsell and affiliate. On not_found, data.product is null.
Does the creator directory cover every Stan Store creator?
GET /v1/stan-store/creators returns one page of creators with handle, profileUrl and productPageCount, plus page.hasMore and page.nextCursor. productPageCount is the number of product-page URLs for that creator; it is null when a page boundary splits the creator's block and the count is incomplete. A null count never matches hasProducts=false.
Why can a filtered directory page be empty?
A prefix or hasProducts match can sit on a later page, so creators can be empty while page.hasMore is true. Follow page.nextCursor until the match appears or page.hasMore is false. Each page is one request and one credit.
Does the products list include every product page that exists?
No. GET /v1/stan-store/creators/{handle}/products lists the products the creator shows on the store page. A product page can exist without being shown there, and those pages are not included in products or in productPageCount. includesUnlisted is always false to make that scope explicit. If you already have a slug for one of those pages, the product route still reads it.
Why is listed null on a product?
listed is true or false when the product can be compared with the creator's listed store, and null when that comparison could not be completed. A null value is unknown, not proof that the product is unlisted.
How do meeting slots and webinar sessions work?
Call GET /v1/stan-store/creators/{handle}/products/{slug}/availability with optional timezone, startDate and endDate query parameters. The default window is the next 14 days in the requested timezone, capped by the product's booking window, and an endDate earlier than startDate is a 400. A meeting returns kind meeting and slots with start and end. A webinar returns kind webinar and sessions with start, end, timezone, availableSeats and bookedSeats. A product that takes no bookings returns kind none with empty slots and sessions. A found meeting can still have zero free slots in the requested window.
What does lookupStatus mean on these routes?
HTTP 200 means the request finished. data.lookupStatus tells you what it found. found means the creator, product or booking answer was returned. not_found means it was not. On a product availability miss, product can still be present when the product exists but its booking details do not, so check kind and the arrays as well as lookupStatus.
When is reason deleted or never_existed?
reason is set on a not_found creator when the storefront distinguishes a deactivated store from a handle that never existed. It is null when the answer does not make that distinction. Do not treat a null reason as found.
Are createdAt and updatedAt always present?
No. Product createdAt and updatedAt are ISO 8601 strings when the storefront supplies them and null otherwise. Price fields are also nullable: amount is null when no price is shown, and 0 means free.
Whose currency is in a product price?
product.price.currency is the creator's display currency, the same currency the storefront uses for that creator's prices. The creator-level currency is the same value.
How much does the Stan Store API cost?
Every Stan Store route costs 1 credit per completed request, including each page of the creator directory. Check meta.creditsCharged on every response. New accounts start with 100 free credits, and pay-as-you-go credits do not expire.
Can I use Stan Store data from MCP or Ask AI?
Yes. Every Stan Store route is available as a typed MCP tool and through Ask (POST /v1/ask) in plain English. The REST routes are the better choice for scheduled production jobs and for exact field control.
The Stan Store API in detailHow the Stan Store routes work, what they cost, and how they differ from the official API.
Why teams use Social Fetch for Stan Store
Stan Store storefronts mix a creator profile, a list of products and optional booking pages. Social Fetch exposes five routes under /v1/stan-store: one creator profile, that creator's listed products, one product in full, that product's availability, and a creator directory.
The creator route returns profile (handle, displayName, bio, avatarUrl, profileUrl, verified), socials, paymentMethods, language, currency, termsText, storeId, storeName, sections and products. verified is always null: Stan Store has no verification mark. The product list returns products and productPageCount. The single product route adds price, descriptionLinks, descriptionImages, inventory, questions, reviews, course, meeting, webinar, upsell, affiliate, communityEnabled and the call-to-action fields.
Availability answers with kind (meeting, webinar or none), timezone, startDate, endDate, slots and sessions. The directory pages with page.nextCursor. Every route returns HTTP 200 for found and not found, so branch on lookupStatus. createdAt and updatedAt are null when a storefront does not supply them.
How to call the Stan Store API
1. Create an API key
Sign up at Social Fetch and copy a key (
sfk_…). New accounts get 100 free credits, enough to try all five Stan Store routes on a few stores.2. Pick the route
Use
GET /v1/stan-store/creators/{handle}for a profile,GET /v1/stan-store/creators/{handle}/productsfor the store list,GET /v1/stan-store/creators/{handle}/products/{slug}for one product, and add/availabilityfor slots or sessions. Sendx-api-keyon every request.3. Branch and page
Check
data.lookupStatusbefore storing a row. For the directory, keep the sameprefixandhasProductsfilters and passpage.nextCursorback ascursorwhilepage.hasMoreis true.
What each Stan Store route returns
- One creator's profile, social links, connected payment methods, store sections and every listed product.
- Listed products in store order, with
productPageCountand every description link and image kept alongside the text. - Full product detail: price and currency, inventory, checkout questions, reviews, course outline, meeting or webinar settings, upsell and affiliate terms.
- Free meeting slots and upcoming webinar sessions, with
availableSeatsandbookedSeatswhen the product books sessions. - A creator directory, filterable by handle prefix and by whether a creator has product pages.
- Typed
not_foundoutcomes with areasonwhen the storefront distinguishes a deleted store from a handle that never existed.
How much does the Stan Store API cost?
Each Stan Store route costs 1 credit per completed request. A directory page is one request, and limit controls how many creators that request returns, not how many credits it costs. Credits never expire on pay-as-you-go packs. meta.creditsCharged on every response is the billing source of truth.
Social Fetch vs the official Stan Store API
Stan Store does not publish a developer API for creator storefronts. Creator and product details are public on the storefront, and booking availability is part of the same public experience. Social Fetch turns that into one JSON contract: the same field names across every creator, typed not_found outcomes, booking slots and sessions in one shape, and a directory endpoint for discovery.
Pull your first Stan Store data.
Run a live Stan Store request in the playground. 100 free credits, no card, JSON back in seconds.
No credit cardSign up in 30 seconds withGoogleGitHub