TutorCruncher · Rate Limits

Tutorcruncher Rate Limits

TutorCruncher publishes a single, explicit REST API rate limit: 100 API requests per minute per account. This applies across all endpoints and should be respected when running bulk operations. Beyond the request-rate cap, list-based GET requests are paginated at 100 objects per page, which bounds response size and encourages cursor-style paging via the `next` URL. Webhook delivery has its own retry/backoff behavior rather than a request-rate limit.

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

It captures 3 rate-limit definitions, measuring requests, objects, and deliveries.

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

Tagged areas include Tutoring, Education, Rate Limiting, Quotas, and Pagination.

3 Limits Throttle: 429
TutoringEducationRate LimitingQuotasPagination

Limits

REST API Requests account
requests
100 per minute
Explicit documented limit across all API endpoints.
List Pagination request
objects
100 per page
All list-based GET endpoints return up to 100 objects per page with count/next/previous/results.
Webhook Delivery Retries integration
deliveries
up to 4 retries with exponential backoff (1s, 10s, 100s, 1000s)
Retries fire on timeout, non-response, or 5xx. Endpoints exceeding a 20% failure rate are auto-disabled.

Policies

Bulk Operation Pacing
Stay under 100 requests/minute for bulk operations; page through large result sets via the next URL rather than issuing many parallel requests.
Backoff Strategy
On a 429 response, back off and retry; implement exponential backoff with jitter.
Webhook Reliability
Webhook endpoints must return promptly and with 2xx; sustained failures (>20%) auto-disable the integration and must be re-enabled.

Sources