Softr · Rate Limits

Softr Rate Limits

The Softr Database API enforces per-token rate limits: read operations (GET and POST /search) are limited to 40 requests/second and write operations (POST, PUT, PATCH, DELETE) to 30 requests/second. Exceeding a limit returns HTTP 429. Published-app subscription allowances (app users, Softr Database records, AI credits, Workflow actions) act as plan-level quotas. Per-second limits for the Users Management API are not separately documented.

Softr Rate Limits is the machine-readable rate-limit profile for Softr on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests, records, users, and actions.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include No Code, App Builder, Database, User Management, and Rate Limiting.

6 Limits Throttle: 429
No CodeApp BuilderDatabaseUser ManagementRate LimitingQuotasThrottling

Limits

Database API Reads token
requests
40 per second
Applies to GET requests and POST /search on the Softr Database API.
Database API Writes token
requests
30 per second
Applies to POST, PUT, PATCH, and DELETE on the Softr Database API.
Users Management API token
requests
see provider documentation
No per-second rate limit is separately documented for studio-api.softr.io.
Softr Database Records account
records
plan-dependent (5,000 Free to 1,000,000 Business)
Subscription-level quota on stored records; varies by plan.
App Users account
users
plan-dependent (10 Free to 500 Business)
Subscription-level quota on published-app end users; varies by plan.
Workflow Actions account
actions
plan-dependent (500 Free to 25,000 Business per month)
Monthly subscription-level quota on Workflow automation actions.

Policies

Tiered Quotas
Record, app-user, AI-credit, and Workflow-action allowances rise with the subscription plan and are custom on Enterprise.
Backoff Strategy
On HTTP 429 the Softr Database API recommends implementing backoff logic and retrying after a brief pause.

Sources