Pillar API

Endpoints

Quick start

Coverage & limits

• One public profile per request; four concurrent requests per worker. Saturation returns 503 busy.
• 15-second total deadline and at most five upstream requests, including one shared retry for network errors or HTTP 5xx. Redirects are rejected; 429 and access challenges are not retried.
• A cold request reads the public shop, page bootstrap, current client bundle, and account metadata. Subsequent requests normally need only shop and account reads. Tokens are sent only to Pillar’s fixed GraphQL endpoint, never to outbound URLs or other workers.
• 2 MiB total decoded bytes across shop JSON, client bootstrap, client source, and account response. Shop JSON is limited to nesting depth 16 and 20,000 nodes. Payload limits fail explicitly.
• At most 500 visited links and products combined, processed in that order, and 100 social channels. Record limits produce partial coverage.
• Private, password-protected, or consent-gated profiles answer an explicit restricted failure; gated records are reported with a warning.
• Missing collections return empty arrays with warnings. Missing metrics return null; they are never substituted with zero. Empty public collections do not add a missing-collection warning.
• Coverage includes public profile fields, custom links, and featured products.
• Fresh public API reads only. The ordinary logged-out frontend credential is discovered from Pillar’s current public client and retained only in memory for up to 15 minutes or its expiry. No account login, cookie jar, destination visits, result caching, billing, or customer key management. No production domain is assumed.
• Retrieval fails explicitly rather than returning a reduced record when the public client changes.