Skip to content

List analysis runs for a plot

Request

Returns all analysis runs associated with the provided plot_id. Each item summarizes the run, including the check type, effective configuration, status, timing, tokens cost, and links to artifacts. A plot accumulates one run per check per job, so re-running an analysis with a different configuration produces a new, auditable run.

Security
BearerAuth
Query
plot_idstringrequired

Plot ID to list runs for

Headers
Authorizationstring

Authorization header with a Bearer token, formatted as 'Bearer [JWT]' where [JWT] is the JSON Web Token used for user authentication and authorization.

Example:Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.your-payload-here.signature
GET
/analysis-runs
curl -i -X GET \
  'https://api.open-atlas.com/_mock/openapi/analysis-runs?plot_id=string' \
  -H 'Authorization: Bearer <YOUR_JWT or vantage_live_ API key_HERE>'

Responses

Successful response

Bodyapplication/json
Array [
run_idstring

Unique identifier of this analysis run

job_idstring

The job this run belongs to

plot_idstring

The plot this run analyzed

check_typestring

The analysis capability that was run, e.g. 'eudr', 'protected_area', 'soil_moisture', 'visual_verification'

Example:"eudr"
effective_configobject

The exact configuration used for this run, after merging plot metadata, job-level config, and per-plot overrides

Example:
{ "harvest_date": "2024-11-01", "commodity": "cocoa" }
statusstring

Current status of this analysis run

errorstring

Error message when the run failed

analysis_imagestring

URL of the generated visualization artifact, when the capability produces one

tokens_costinteger, (int32)

Tokens consumed by this run

created_atstring

Timestamp when the run was created

updated_atstring

Timestamp when the run was last updated

analysisobject(Analysis)

Complete analysis data for a plot. Legacy top-level fields (risk_level, deforestation, forest_*, etc.) are written by the EUDR bundle for backwards compatibility; the same data is also available under the eudr key. Every other analysis capability writes its result under a key matching the capability name (e.g. soil_moisture, flood_risk_5years, solar_site_suitability) using the standard capability result envelope, except where a dedicated schema is documented (visual_verification, deforestation_analysis, GEE checks). The protected_area check writes under protected_areas and the indigenous_land check under indigenous_land.

]
Response
[ { "run_id": "string", "job_id": "string", "plot_id": "string", "check_type": "eudr", "effective_config": {}, "status": "string", "error": "string", "analysis_image": "string", "tokens_cost": 0, "created_at": "string", "updated_at": "string", "analysis": {} } ]