Overview

Retrieve your site’s public configuration — enabled features, products and plans, paywalls, newsletters, payment gateway settings, and design settings. Call this first, before rendering any customer-facing flow, so your front end knows what is available and how to behave.

Example: On page load, fetch the site configuration to decide which paywall to show, which plans to offer, and which payment methods to display.

Edge-cached for speed

This endpoint is heavily edge-cached, so it typically responds in under 80 ms. Responses are cached for about 5 minutes.

🚧

Configuration changes are not instant

Because of the ~5-minute cache window, a change made in the dashboard can take up to about 5 minutes to appear here. Do not rely on this endpoint for real-time state.

Notes

• Public endpoint. Only a valid site_id is required — no authentication token is needed.
• The call can be made directly from a browser or front-end app.
• A missing or invalid site_id returns a 400 response.