invalid-body
| Status | 400 |
| Title | Invalid request body |
| Code | invalid-body |
| Type | https://docs.satellitedata.net/problems/invalid-body |
Available now Lean v1 can return this problem.
Meaning
Section titled “Meaning”A JSON body is malformed, has an unknown member, or has a value of the wrong type or range.
Likely causes
Section titled “Likely causes”- Invalid JSON, for example a trailing comma.
- A misspelt member such as
maxCloudCoverinstead ofmaxCloudCoverage. Unknown members are rejected rather than ignored, so a typo cannot silently widen a search. - A value out of range, such as
output.widthof 0. - A member of the full contract that lean v1 does not offer yet, such as
expression,preset,processing.cloudMask, a second data source or a non-TIFFoutput.format. - An
output.sampleTypethat does not match theunitsandharmonizeasked for.
Check errors[]: each entry has a JSON Pointer (such as /output/width) and what is wrong with that member.
Example
Section titled “Example”The detail is the example from the v1 contract.
{ "type": "https://docs.satellitedata.net/problems/invalid-body", "title": "Invalid request body", "status": 400, "detail": "output.width must be an integer from 1 to 2500.", "instance": "/v1/...", "code": "invalid-body", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}See Errors for the members every problem carries.