Documentation

Pagoti exposes both origin-restricted public endpoints for frontends and token-protected private endpoints for backend and automation workflows. Use this overview to choose the right surface, then dive into the dedicated guides for implementation details.

Commerce

Connections

Connect a Stripe account to a project to enable commerce features.

Add a connection →

API guides

Public API

Origin-protected, read-only access for browser clients, static-site generators, and edge runtimes. Perfect when you need to fetch published content in environments where storing secrets is not an option.

Explore the Public API guide →

Private API

Token-authenticated access for servers, CI/CD pipelines, and automation tooling. Use it to pull both published and unpublished content from anywhere with network access.

Explore the Private API guide →

Rate limiting

Both APIs enforce rate limits that scale with your plan. Exceeding the allowance results in 429 Too Many Requests.

Use caching, queue retries with exponential backoff, and monitor the dashboard for quota details.

Best practices

1. Cache responses wherever possible to reduce API traffic
2. Use webhooks (coming soon) to react to content changes
3. Handle 403, 404, and 429 responses gracefully
4. Prefer slugs for readability when referencing resources
5. Implement pagination handling for large result sets