Skip to documentation

Generic examplesSign in to personalize workspace URLs.

Download OpenAPI

Plans and limits

The current catalog is Free, Starter, Growth and Scale, limited by active projects pooled across the organization. Subscriptions sold before it keep their legacy Free/Entry/Growth caps until migrated, so a plan id always comes with its catalogVersion (v2 current, v1 legacy) — legacy Growth is not the current Growth. Both tables come from the same caps used by the app/API. Current effective entitlement, trial and usage still matter.

Allowancefreestartergrowthscale
clients1unlimitedunlimitedunlimited
projectsunlimitedunlimitedunlimitedunlimited
activeProjects131030
dataWindowDays90365365365
reportsPerMonth220100unlimited
syncFrequencyweeklydailydailyhourly
qaAccessfalsetruetruetrue
distributionRecipients325unlimitedunlimited
scheduledBundles110unlimitedunlimited
customRolesfalsefalsefalsetrue
includedCreditsPerPeriod030012004000

Legacy contracts (catalog v1, honored until migrated):

Allowancefreeentrygrowth
clients1525
projects115100
activeProjectsunlimitedunlimitedunlimited
dataWindowDays90365365
reportsPerMonth220unlimited
syncFrequencyweeklydailyhourly
qaAccessfalsetruetrue
distributionRecipients325unlimited
scheduledBundles110unlimited
customRolesfalsefalsetrue
includedCreditsPerPeriod000

Technical safety limits

UTC minute buckets: 120 reads and 30 writes per key; 600 reads and 120 writes per workspace. These are default technical safety limits; a deployment may configure different values. They are separate from plan quotas. Uploads accept at most 5242880 bytes and 50000 rows. Honor the actual Retry-After header.

Saved-report monthly quotas differ from read access, previews, safety buckets and provider budgets. Eligible-plan badges do not override current creator role, ownership, data access or reportable window. Custom roles are a Scale capability (legacy Growth keeps them); Q&A follows implemented policies; there is no extra Enterprise claim.

Evidence and administration

Sync cadence is eligibility, not proof a provider connection exists or succeeded. Provider consent, organization/workspace lifecycle, membership, sharing, recipients, billing payments and distribution remain app workflows. See error recovery.

Search documentation

Enter a word or phrase to search documentation.