Cropio · Rate Limits

Cropio Rate Limits

Cropio (Cropwise Operations Platform API v3) does not publish any numeric per-minute, per-hour, or per-day request rate limit in its documentation. The documented HTTP response codes cover 200/201/204/400/401/403/404/422/503 - there is no 429 Too Many Requests code documented and no throttling policy described anywhere in the Apiary reference. The main documented control on response size is a per-resource pagination limit (`limit`/`from_id` query parameters), not a request-rate limit.

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

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

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

Tagged areas include Agriculture, AgTech, Precision Agriculture, Rate Limiting, and Quotas.

3 Limits Throttle: not documented
AgricultureAgTechPrecision AgricultureRate LimitingQuotas

Limits

Resource Collection Page Size endpoint
records
mostly 1000 records per request (per-resource default/maximum)
Controlled via the `limit` and `from_id` query parameters on `GET /api/v3/{resource}`; requesting more than the resource's maximum silently falls back to that maximum.
API Request Rate account
requests
not published
No documented per-minute/hour/day request-rate limit for any endpoint.
GPS/Telematics Query Window endpoint
requests
requires explicit date_at (or from_time/to_time) and machine_ids filters
GpsLoggerDataItems and GpsAggregatedData require a date/time filter on every call (open-ended queries are not permitted); this bounds response size rather than request rate. Marked "Testing stage, may be changed."

Policies

Pagination via limit/from_id
List endpoints return `data` plus a `meta.response` block with `obtained_records`, `first_record_id`, and `last_record_id`, used to page through large collections with repeated `from_id` requests.
Changes/Changes Ids Polling
Most resources expose `GET /{resource}/changes` and `/changes_ids` with `from_time`/`to_time` filters, intended as the documented pattern for polling for incremental updates rather than re-fetching full collections.
Service Maintenance
A documented 503 Service Unavailable response indicates scheduled platform maintenance; clients are told to retry later, implying no formal SLA on availability during maintenance windows.

Sources