> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/stan-store/creators-handle>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/stan-store/creators-handle.mdx>

---

# Stan Store Creator API

One creator profile with their socials, store sections and every product they list, in a single response.

`GET /v1/stan-store/creators/{handle}` takes the handle as it appears on the storefront and returns `lookupStatus`, `reason`, `profile`, `socials`, `paymentMethods`, `language`, `currency`, `termsText`, `storeId`, `storeName`, `sections` and `products`.

On found, `profile` carries `handle`, `displayName`, `bio`, `avatarUrl`, `profileUrl` and `verified`, which is always null because Stan Store has no verification mark. `paymentMethods` lists `stripe` or `paypal` only when the creator connected them. `currency` is the creator's display currency, the same currency used for the prices in `products`. `sections` groups the store and `products` holds every page the creator lists, in store order, each with `slug`, `type`, `title`, `price` and `createdAt` or `updatedAt` when the storefront supplies dates.

On not found, `profile` is null, the lists are empty, and `reason` is `deleted` or `never_existed` when the storefront makes that distinction. A handle is 2 to 47 letters, digits, dots, underscores or hyphens, and the canonical case comes back in `profile.handle`.

## Request

- **Endpoint:** `GET /v1/stan-store/creators/{handle}`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by handle
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/stan-store/creators/handle/get)
- **Platform page:** [/platforms/stan-store](https://www.socialfetch.dev/platforms/stan-store)

## FAQ

### What is in the products array?

Every page the creator lists, in store order. Each row has id, productId, slug, type, title, description, descriptionLinks, descriptionImages, imageUrl, tagline, buttonText, cardImageUrl, price, link, paymentOptions, createdAt, updatedAt, order, listed and section. For the full record of one product, call the product route with its slug.

### When is reason set?

reason is deleted or never_existed on a not_found creator when the storefront distinguishes a deactivated store from a handle that never existed. It is null when that distinction is not available. HTTP 200 only means the request finished, so branch on lookupStatus.

### Why is paymentMethods empty?

paymentMethods contains only what the creator has connected, stripe, paypal, or both. An empty array means no payment method was listed on the page, not that checkout is necessarily unavailable.

### How many credits does a creator lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.

### Are createdAt and updatedAt guaranteed?

No. They are ISO 8601 strings when the storefront supplies them and null otherwise. Do not build an ordering or freshness job that assumes every product has both.