DroneDeploy · Rate Limits

Dronedeploy Rate Limits

DroneDeploy does not publish fixed numeric rate limits for its GraphQL API in the public developer documentation. Practical throughput is governed more by cursor-based pagination (the `first` argument caps the number of results per query, with examples using page sizes of 5-50) and by asynchronous, long-running processing (map exports and reports must reach status COMPLETE before a downloadPath is available) than by a per-minute request cap. Because API access is Enterprise / Developer Partner only, any enforced quotas are typically set per contract.

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

It captures 4 rate-limit definitions, measuring requests, results, exports, and gigapixels.

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

Tagged areas include Drone Mapping, Reality Capture, GraphQL, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Drone MappingReality CaptureGraphQLRate LimitingQuotas

Limits

GraphQL API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the GraphQL endpoint; limits, if any, are set per Enterprise/Developer Partner contract.
Pagination Page Size query
results
bounded by `first` argument
Relay connections cap results via `first`; documented examples use first=5 and first=50. Retrieve more with `after` + endCursor.
Export Processing account
exports
asynchronous
createExport is async; poll export status until COMPLETE before using downloadPath. Concurrency is contract-dependent.
Processing Volume account
gigapixels
per plan
Map processing is metered by images-per-map and annual Gigapixel allowances tied to the subscription tier, not by API request rate.

Policies

Cursor Pagination
Use `first` with `after`/endCursor for forward pagination; check pageInfo.hasNextPage to know when to stop.
Asynchronous Processing
Exports and reports are long-running; create the job, then poll for status COMPLETE (or register a completion webhook) rather than blocking.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.

Sources