Point or small-polygon time series
const url = 'https://api.satellitedata.net/v1/timeseries';const options = { method: 'POST', headers: {'X-API-Key': '<X-API-Key>', 'Content-Type': 'application/json'}, body: '{"geometry":{"type":"Polygon","coordinates":[[[-93.262,44.941],[-93.252,44.941],[-93.252,44.947],[-93.262,44.947],[-93.262,44.941]]]},"collections":["optical-sr"],"datetime":"2026-06-01T00:00:00Z/2026-08-31T23:59:59Z","index":"ndvi","harmonize":"bandpass_adjusted","cloudMask":{"exclude":["nodata","saturated_defective","cloud","cloud_shadow","cirrus","cloud_adjacent"],"scl7":"cloud","dilate_m":150},"reducer":"median","format":"json"}'};
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/timeseries \ --header 'Content-Type: application/json' \ --header 'X-API-Key: <X-API-Key>' \ --data '{ "geometry": { "type": "Polygon", "coordinates": [ [ [ -93.262, 44.941 ], [ -93.252, 44.941 ], [ -93.252, 44.947 ], [ -93.262, 44.947 ], [ -93.262, 44.941 ] ] ] }, "collections": [ "optical-sr" ], "datetime": "2026-06-01T00:00:00Z/2026-08-31T23:59:59Z", "index": "ndvi", "harmonize": "bandpass_adjusted", "cloudMask": { "exclude": [ "nodata", "saturated_defective", "cloud", "cloud_shadow", "cirrus", "cloud_adjacent" ], "scl7": "cloud", "dilate_m": 150 }, "reducer": "median", "format": "json" }'Returns a time series for a point or a polygon of at most 25 square kilometres, reducing the pixels of each overpass with mean, median, min or max. It takes the full cloud-mask object and an expression in the body, which suits sentinelhub-py style clients that build requests as JSON.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”Time series request.
Point or small-polygon time series request. Polygons may cover at most 25 km2.
object
A GeoJSON geometry.
object
GeoJSON geometry type.
GeoJSON coordinates in CRS84 longitude and latitude (RFC 7946).
Collections or aliases.
RFC 3339 interval; at most 15 years.
Schema v1 index id.
Band math instead of index.
Harmonization level.
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.
Scene cloud cover ceiling.
How polygon pixels reduce to one value.
Response format.
Example
{ "geometry": { "type": "Polygon", "coordinates": [ [ [ -93.262, 44.941 ], [ -93.252, 44.941 ], [ -93.252, 44.947 ], [ -93.262, 44.947 ], [ -93.262, 44.941 ] ] ] }, "collections": [ "optical-sr" ], "datetime": "2026-06-01T00:00:00Z/2026-08-31T23:59:59Z", "index": "ndvi", "harmonize": "bandpass_adjusted", "cloudMask": { "exclude": [ "nodata", "saturated_defective", "cloud", "cloud_shadow", "cirrus", "cloud_adjacent" ], "scl7": "cloud", "dilate_m": 150 }, "reducer": "median", "format": "json"}Responses
Section titled “Responses”Time series, oldest first.
Time series.
object
A GeoJSON geometry.
object
GeoJSON geometry type.
GeoJSON coordinates in CRS84 longitude and latitude (RFC 7946).
Collections searched.
Index or expression evaluated.
Harmonization level.
Observations returned.
Observations, oldest first, one per de-duplicated overpass.
One observation in a time series.
object
Acquisition time.
Item id.
Native collection.
Platform.
Index or band value; null when every pixel is masked.
Share of pixels not masked.
Level applied to this scene.
Credit line.
Example
{ "geometry": { "type": "Polygon", "coordinates": [ [ [ -93.262, 44.941 ], [ -93.252, 44.941 ], [ -93.252, 44.947 ], [ -93.262, 44.947 ], [ -93.262, 44.941 ] ] ] }, "collections": [ "optical-sr" ], "index": "ndvi", "harmonize": "bandpass_adjusted", "count": 4, "series": [ { "datetime": "2026-06-12T17:21:20Z", "itemId": "S2C_T15TVK_20260612T171605_L2A", "collection": "sentinel-2-l2a", "platform": "sentinel-2c", "value": 0.518, "validFraction": 1, "harmonization": "bandpass_adjusted" }, { "datetime": "2026-06-24T16:58:28Z", "itemId": "LC09_L2SP_027029_20260624_02_T1", "collection": "landsat-ot-l2", "platform": "landsat-9", "value": null, "validFraction": 0, "harmonization": "offset_removed" }, { "datetime": "2026-07-12T17:21:21Z", "itemId": "S2C_T15TVK_20260712T171233_L2A", "collection": "sentinel-2-l2a", "platform": "sentinel-2c", "value": 0.781, "validFraction": 1, "harmonization": "bandpass_adjusted" }, { "datetime": "2026-07-18T16:58:29Z", "itemId": "LC08_L2SP_027029_20260718_02_T1", "collection": "landsat-ot-l2", "platform": "landsat-8", "value": 0.769, "validFraction": 1, "harmonization": "offset_removed" } ], "attribution": "Contains modified Copernicus Sentinel data 2026; Landsat data courtesy of the U.S. Geological Survey"}Example
datetime,itemId,collection,platform,value,validFraction,harmonization2026-06-12T17:21:20Z,S2C_T15TVK_20260612T171605_L2A,sentinel-2-l2a,sentinel-2c,0.518,1,bandpass_adjusted2026-06-24T16:58:28Z,LC09_L2SP_027029_20260624_02_T1,landsat-ot-l2,landsat-9,,0,offset_removedHeaders
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 SurveyBad coordinates, interval or index.
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-parameter", "title": "Invalid parameter", "status": 400, "detail": "datetime must be an interval of at most 15 years.", "instance": "/v1/timeseries", "code": "invalid-parameter", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "errors": [ { "pointer": "datetime", "detail": "interval longer than 15 years" } ]}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 geometry is too large or the expression names a band that does not resolve.
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/area-too-large", "title": "Area too large", "status": 422, "detail": "The polygon covers 61.2 km2; time series polygons may cover at most 25 km2. Use POST /v1/statistics.", "instance": "/v1/timeseries", "code": "area-too-large", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "limits": { "maxAreaKm2": 25, "requestedAreaKm2": 61.2 }}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