Render or extract an area
const url = 'https://api.satellitedata.net/v1/process';const options = { method: 'POST', headers: {'X-API-Key': '<X-API-Key>', 'Content-Type': 'application/json'}, body: '{"input":{"bounds":{"bbox":[-93.3,44.9,-93.2,45]},"data":[{"type":"optical-sr","dataFilter":{"timeRange":{"from":"2026-06-01T00:00:00Z","to":"2026-08-31T23:59:59Z"},"platform":["landsat-8","landsat-9","sentinel-2a","sentinel-2b","sentinel-2c"],"maxCloudCoverage":40,"mosaickingOrder":"leastCC"},"processing":{"units":"REFLECTANCE","harmonize":"bandpass_adjusted","cloudMask":{"exclude":["nodata","saturated_defective","cloud","cloud_shadow","cirrus","cloud_adjacent"],"dilate_m":150}}}]},"bands":["red","nir08"],"expression":"(nir08 - red) / (nir08 + red)","output":{"width":512,"height":512,"format":"image/tiff","sampleType":"FLOAT32"}}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.satellitedata.net/v1/process \ --header 'Content-Type: application/json' \ --header 'X-API-Key: <X-API-Key>' \ --data '{ "input": { "bounds": { "bbox": [ -93.3, 44.9, -93.2, 45 ] }, "data": [ { "type": "optical-sr", "dataFilter": { "timeRange": { "from": "2026-06-01T00:00:00Z", "to": "2026-08-31T23:59:59Z" }, "platform": [ "landsat-8", "landsat-9", "sentinel-2a", "sentinel-2b", "sentinel-2c" ], "maxCloudCoverage": 40, "mosaickingOrder": "leastCC" }, "processing": { "units": "REFLECTANCE", "harmonize": "bandpass_adjusted", "cloudMask": { "exclude": [ "nodata", "saturated_defective", "cloud", "cloud_shadow", "cirrus", "cloud_adjacent" ], "dilate_m": 150 } } } ] }, "bands": [ "red", "nir08" ], "expression": "(nir08 - red) / (nir08 + red)", "output": { "width": 512, "height": 512, "format": "image/tiff", "sampleType": "FLOAT32" } }'Renders or extracts an area: bounds, one to four data sources with filters and processing options, bands or an expression, and an output size and format up to 2,500 by 2,500 pixels. Units are computed before any S3 read, and the request fails with 413 or 422 when a cap is exceeded. Outputs above 4 MB, which would not fit the 6 MB Lambda response limit once base64-encoded, answer 303 with a CloudFront URL into the results bucket.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”Process request.
Process request, modelled on the Sentinel Hub Process API without evalscripts.
object
Inputs.
object
Area of interest: bbox or geometry, not both.
object
Bounding box as [west, south, east, north] in CRS84 longitude and latitude, or six numbers with heights.
A GeoJSON geometry.
object
GeoJSON geometry type.
GeoJSON coordinates in CRS84 longitude and latitude (RFC 7946).
Bounds properties.
object
CRS of bbox or geometry as an OGC URI.
Input collections. More than one is data fusion.
One input collection.
object
Collection id or alias, for example optical-sr or S2L2A.
Name for this source when the request fuses several, used as a prefix in expressions (s1.vv).
Which scenes feed the request.
object
Acquisition time window.
object
Inclusive start, RFC 3339 UTC.
Inclusive end, RFC 3339 UTC.
Maximum scene cloud cover percentage.
Scene order for mosaics.
Normalized platform names such as landsat-9 or sentinel-2c.
On optical-sr, which copy wins when native and HLS observe the same overpass.
Extra CQL2 JSON filter on queryables.
object
How values are converted.
object
Output unit. Defaults per band from schema v1.
Harmonization level. Default offset_removed on native collections and bandpass_adjusted on optical-sr.
Unified cloud mask settings from schema v1.
object
Mask classes to drop. Defaults to schema v1 defaultExclude for statistics and time series and to the preset value for tiles.
How Sentinel-2 SCL class 7 is treated.
Buffer in metres around cloud and cloud_shadow on sources without one.
Minimum Landsat QA_PIXEL cloud confidence counted as cloud.
Clip negative reflectance to 0.
Resampling method.
How overlapping scenes combine into one value.
DEM only: return ellipsoidal heights instead of orthometric.
Render preset id, used instead of bands and expression.
Bands to read by common name, native name or alias. mask, mask_class and dataMask are free.
Band math over the named bands, or a schema v1 index id such as ndvi. Semicolons separate output bands.
Output size and format.
object
Output width in pixels.
Output height in pixels.
Pixel width in CRS units, instead of width.
Pixel height in CRS units, instead of height.
Output CRS as an OGC URI or EPSG code.
Output media type.
Output sample type.
Min and max mapped to 0-255 for AUTO.
Named colormap for one-band images, for example rdylgn.
Examples
Cross-sensor NDVI as a 512 x 512 FLOAT32 GeoTIFF
{ "input": { "bounds": { "bbox": [ -93.3, 44.9, -93.2, 45 ] }, "data": [ { "type": "optical-sr", "dataFilter": { "timeRange": { "from": "2026-06-01T00:00:00Z", "to": "2026-08-31T23:59:59Z" }, "platform": [ "landsat-8", "landsat-9", "sentinel-2a", "sentinel-2b", "sentinel-2c" ], "maxCloudCoverage": 40, "mosaickingOrder": "leastCC" }, "processing": { "units": "REFLECTANCE", "harmonize": "bandpass_adjusted", "cloudMask": { "exclude": [ "nodata", "saturated_defective", "cloud", "cloud_shadow", "cirrus", "cloud_adjacent" ], "dilate_m": 150 } } } ] }, "bands": [ "red", "nir08" ], "expression": "(nir08 - red) / (nir08 + red)", "output": { "width": 512, "height": 512, "format": "image/tiff", "sampleType": "FLOAT32" }}The same NDVI as JSON for a 2 x 2 pixel box
{ "input": { "bounds": { "bbox": [ -93.255, 44.945, -93.245, 44.955 ], "properties": { "crs": "http://www.opengis.net/def/crs/OGC/1.3/CRS84" } }, "data": [ { "type": "optical-sr", "dataFilter": { "timeRange": { "from": "2026-06-01T00:00:00Z", "to": "2026-08-31T23:59:59Z" }, "platform": [ "landsat-8", "landsat-9", "sentinel-2a", "sentinel-2b", "sentinel-2c" ], "maxCloudCoverage": 40, "mosaickingOrder": "leastCC" }, "processing": { "units": "REFLECTANCE", "harmonize": "bandpass_adjusted", "cloudMask": { "exclude": [ "nodata", "saturated_defective", "cloud", "cloud_shadow", "cirrus", "cloud_adjacent" ], "dilate_m": 150 } } } ] }, "bands": [ "red", "nir08" ], "expression": "(nir08 - red) / (nir08 + red)", "output": { "width": 2, "height": 2, "crs": "EPSG:4326", "format": "application/json" }}Responses
Section titled “Responses”The rendered or extracted raster. GeoTIFF outputs carry raster:scale and raster:offset tags; JSON returns values for outputs up to 65,536 pixels.
JSON output of POST /v1/process, for outputs up to 65,536 pixels.
object
Output CRS.
Bounding box as [west, south, east, north] in CRS84 longitude and latitude, or six numbers with heights.
Columns.
Rows.
Output band names.
Unit id of the values, or null for band-math outputs such as indices, which are unitless.
Value used for masked pixels; null in JSON.
Values as bands, then rows from north, then columns from west. Masked pixels are null.
Scenes used and the harmonization applied to each.
One scene that contributed to an output, with the harmonization applied.
object
Item id.
Native collection.
Platform.
Acquisition time.
Level actually applied to this scene.
Mask source used.
Share of output pixels this scene supplied.
Credit line for the scenes used.
Example
{ "crs": "EPSG:4326", "bbox": [ -93.255, 44.945, -93.245, 44.955 ], "width": 2, "height": 2, "bands": [ "ndvi" ], "unit": null, "nodata": null, "values": [ [ [ 0.712, 0.698 ], [ 0.705, null ] ] ], "scenes": [ { "id": "S2C_T15TVK_20260712T171233_L2A", "collection": "sentinel-2-l2a", "platform": "sentinel-2c", "datetime": "2026-07-12T17:21:21Z", "harmonization": "bandpass_adjusted", "maskSource": "scl", "pixelFraction": 0.91 }, { "id": "LC08_L2SP_027029_20260718_02_T1", "collection": "landsat-ot-l2", "platform": "landsat-8", "datetime": "2026-07-18T16:58:29Z", "harmonization": "offset_removed", "maskSource": "qa_pixel", "pixelFraction": 0.09 } ], "attribution": "Contains modified Copernicus Sentinel data 2026; Landsat data courtesy of the U.S. Geological Survey"}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DUnits charged for this response; 0 for cache hits and free routes.
Example
1.333Units left this month before restricted mode.
Example
8664.2Remaining units and seconds to reset in the current window (IETF RateLimit header draft).
Example
"units";r=287;t=41Quota policy of the caller (IETF RateLimit header draft).
Example
"units";q=300;w=60Credit lines for the data in the response, separated by semicolons.
Example
Contains modified Copernicus Sentinel data 2026; Landsat data courtesy of the U.S. Geological SurveyOutput larger than 4 MB: Location is a CloudFront signed URL under /results/ whose origin is the lambda-raster results bucket, valid for one hour; the object expires after 24 hours. Units are charged once.
Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DUnits charged for this response; 0 for cache hits and free routes.
Example
1.333Units left this month before restricted mode.
Example
8664.2Remaining units and seconds to reset in the current window (IETF RateLimit header draft).
Example
"units";r=287;t=41Quota policy of the caller (IETF RateLimit header draft).
Example
"units";q=300;w=60Credit lines for the data in the response, separated by semicolons.
Example
Contains modified Copernicus Sentinel data 2026; Landsat data courtesy of the U.S. Geological SurveyCloudFront signed URL of the output in the results bucket.
Example
https://api.satellitedata.net/results/01JQ7Z3M8R5V2W6X9Y0A1B2C3D.tif?Expires=1792055112&Signature=c2lnbmF0dXJl&Key-Pair-Id=K2JCJMDEHXQW5FMalformed body.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "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/process", "code": "invalid-body", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "errors": [ { "pointer": "/output/width", "detail": "must be <= 2500" } ]}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DThe API key or bearer token is missing, unknown, revoked or expired.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "type": "https://docs.satellitedata.net/problems/invalid-key", "title": "Invalid or missing credentials", "status": 401, "detail": "Send a verified key in X-API-Key or a bearer token from /oauth/token.", "instance": "/v1/process", "code": "invalid-key", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DChallenge naming the accepted schemes.
Example
Bearer realm="satellitedata.net", ApiKey header="X-API-Key"The credentials are valid but cannot use this route, for example before email verification or without the scope.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "type": "https://docs.satellitedata.net/problems/email-unverified", "title": "Email not verified", "status": 403, "detail": "Keys work only after the account email is verified. Check your inbox or resend from the dashboard.", "instance": "/v1/process", "code": "email-unverified", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DThe output or area exceeds a hard cap.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "type": "https://docs.satellitedata.net/problems/output-too-large", "title": "Output too large", "status": 413, "detail": "Requested 4000 x 4000 pixels; the cap is 2500 x 2500.", "instance": "/v1/process", "code": "output-too-large", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "limits": { "maxWidth": 2500, "maxHeight": 2500, "requestedWidth": 4000, "requestedHeight": 4000 }}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DValid JSON that cannot be served: unknown band, unsupported harmonize or units, or too many scenes.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "type": "https://docs.satellitedata.net/problems/harmonize-unavailable", "title": "Harmonization level unavailable", "status": 422, "detail": "nbar is available only on hls and on optical-sr through hls; sentinel-2-l2a supports none, offset_removed and bandpass_adjusted.", "instance": "/v1/process", "code": "harmonize-unavailable", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "errors": [ { "pointer": "/input/data/0/processing/harmonize", "detail": "nbar not supported by sentinel-2-l2a" } ]}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DA per-minute, concurrency, monthly or per-IP limit was hit. Retry-After says when to retry.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "type": "https://docs.satellitedata.net/problems/rate-limited", "title": "Rate limit exceeded", "status": 429, "detail": "This key spent 300 of its 300 units in the current minute.", "instance": "/v1/process", "code": "rate-limited", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "retryAfter": 17, "limits": { "unitsPerMinute": 300, "unitsSpentThisMinute": 300 }}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DSeconds to wait before retrying.
Example
17Remaining units and seconds to reset in the current window (IETF RateLimit header draft).
Example
"units";r=287;t=41Quota policy of the caller (IETF RateLimit header draft).
Example
"units";q=300;w=60An unexpected server error. No units are charged.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "type": "https://docs.satellitedata.net/problems/internal", "title": "Internal error", "status": 500, "detail": "The request failed on our side and was logged. No units were charged.", "instance": "/v1/process", "code": "internal", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DAn upstream catalog or bucket is unavailable, or the service is in maintenance. No units are charged.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "type": "https://docs.satellitedata.net/problems/upstream-unavailable", "title": "Upstream unavailable", "status": 503, "detail": "NASA Earthdata returned 503 for the HLS credentials endpoint; HLS scenes are temporarily unavailable.", "instance": "/v1/process", "code": "upstream-unavailable", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "retryAfter": 120}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DSeconds to wait before retrying.
Example
17The render did not finish within the 29-second API Gateway limit. No units are charged.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
Example
{ "type": "https://docs.satellitedata.net/problems/render-timeout", "title": "Render timed out", "status": 504, "detail": "The render read 41 scenes and did not finish in 29 seconds. Narrow the time range or lower the output size.", "instance": "/v1/process", "code": "render-timeout", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3D