request-too-expensive
| Status | 422 |
| Title | Request too expensive |
| Code | request-too-expensive |
| Type | https://docs.satellitedata.net/problems/request-too-expensive |
Coming later This problem belongs to unit metering, which lean v1 does not have yet.
Meaning
Section titled “Meaning”The request’s estimated units are more than one request may cost on your tier.
Likely causes
Section titled “Likely causes”- A single request estimated above the tier’s
maxUnitsPerRequest(300 units on the free tier).
Split the request. The problem carries unitsEstimated so you can size the pieces.
Example
Section titled “Example”{ "type": "https://docs.satellitedata.net/problems/request-too-expensive", "title": "Request too expensive", "status": 422, "detail": "The request's estimated units are more than one request may cost on your tier.", "instance": "/v1/...", "code": "request-too-expensive", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}The detail above is a placeholder; the real one names the value at fault.
See Errors for the members every problem carries.