The Panspectra EUDR API
The API lets your own systems do what your people do in the Panspectra app: send plots to be checked for deforestation, read each result, ask your suppliers what a result asks of them, record your conclusion with the evidence it rests on, and file due diligence statements in the EU Information System (TRACES).
It answers at https://eudr-api.panspectra.com/v1/, in JSON. Its description in OpenAPI is at /openapi.json, and this guide in Markdown, for the AI tools you may write code with, is at /llms.txt.
A first integration, on a sandbox
A sandbox organisation is one we make for you to try the API on. Its keys begin eudr_test_. Its plots are checked on made-up imagery in a minute or two, cost nothing, and are never counted against a plan; every page of their reports says that it is a sandbox's, and the page that checks a report's code knows none of them. Its statements are filed at once with numbers of their own (SANDBOX-…), never in TRACES. In the app, its questions to suppliers go to its own people alone, who answer them as a supplier would. Ask us for one at support@panspectra.com. Its admin makes its keys in the app, on the organisation's page.
Every request names the key in the Authorization header:
Authorization: Bearer eudr_test_…
1. Send a plot. A plot is a GeoJSON feature: a polygon, or for a plot of 4 hectares or less a point with its area (declared_area_ha), its properties naming its reference (plot_id), its supplier, its country and its commodity.
POST /v1/assessments
Idempotency-Key: 6c1f8f9e-first-send
{"plots": {"type": "FeatureCollection", "features": [{
"type": "Feature",
"geometry": {"type": "Polygon", "coordinates": [[[-54.01, -10.01],
[-53.99, -10.01], [-53.99, -9.99], [-54.01, -9.99], [-54.01, -10.01]]]},
"properties": {"plot_id": "FARM-7", "supplier": "Coop Norte",
"country": "BR", "commodity": "soya"}}]}}
The answer names an assessment of each plot sent, in_progress.
2. Read its result. GET /v1/assessments/{assessment_id} answers the assessment, done once its result stands, with its result, the questions it leaves for the supplier, and links to its report as a PDF and to the page anyone may open to check it. Rather than ask again and again, make a webhook in the app (section 8): it tells you when the result is out.
3. Conclude, where the result asks for the supplier's evidence. Send your conclusion on the risk with the evidence it rests on: POST /v1/assessments/{assessment_id}/conclusion.
4. File a statement. Draft it from the goods and the plots they came from (POST /v1/statements), read it, and file exactly what you read (POST /v1/statements/{statement_id}/file). Its numbers come back when TRACES gives them.
Keys
A key is the organisation's, never a person's, and is made in the app by one of its admins, who sees it once. It outlives its maker's seat, and any admin revokes it at once. An organisation holds at most ten keys at a time, revoked ones not counted. There are two kinds:
- An editor's key does the work: it sends plots, records conclusions, and drafts, files and withdraws statements.
- A viewer's key reads: plots, assessments, reports and statements. A quote creates nothing, so a viewer's key may ask for one.
No key is an admin's: keys, people, roles and webhooks are changed in the app alone. A key may be limited to the addresses your systems call from; a call from any other is refused. Keys work on this API alone: the app's own routes take a person's sign-in.
Every act of a key is recorded under its label, in the organisation's activity, and a statement filed through the API is emailed to the organisation's people naming the key that filed it.
Keys come with a plan. Every plan includes the API. On pay as you go an organisation makes no key, and the keys it made on a plan keep working after the plan ends. A trial organisation makes none, and none works for it (403 forbidden).
Sending plots
POST /v1/assessments/quote says what a send would use of your plan, creating nothing: each plot as our intake reads it (whether it can be checked as supplied, what is wrong with it, what was mended), the plots a send leaves out, and the plan's figures. A plot larger than 20,000 ha is never checked: its problem, above_maximum_area, says how to cut it into plots of its own.
POST /v1/assessments sends them, each its own assessment, numbered on the plot: the plot's first is 1, the next 2. To check plots the library holds again, name them: {"plot_ids": ["FARM-7"]}. A plot the send does not take is named in the answer's left_out with why: being_assessed (it is being checked already), assessed_today (it was checked today as it is now: its result stands until the next day, or until you change the plot), unknown (your library holds no plot of that reference), retired, or invalid (one that cannot be checked as supplied: correct it first). A send that takes none of the plots named is refused, each with its reason.
A plot counts once in 12 months, on every plan, however often it is sent within them, and only as its first report is issued, in the contract year it was sent: a plot whose check is not completed is never counted. A plot larger than 150 ha counts once for every 150 ha begun: an outline by its measured area, a point by the area it declares (4 ha when it declares none), so a plot of 400 ha counts as three. It stays one plot, with one assessment and one result, and the quote's and the send's figures count it so. The quote keeps the plots still being checked out of what is left (pending_before). Plots beyond the plan's allowance are billed at the plan's price, and a send that goes beyond it needs your consent to exactly the figures its quote gave:
{"plots": …, "consent": {"overage_plots": 20, "charge_cents": 2000}}
Without it, nothing is sent or charged, and the refusal (409 consent_needed) gives the fresh figures.
A send takes up to 20,000 plots and 32 MiB; split a larger one.
Retries. Every request that makes or sends something takes an Idempotency-Key: a send, a statement drafted, a conclusion, a filing. Sent again with the same key and the same request, it answers what the first made (200), as it stands now, making nothing again; another request under the same key, on any of these routes, is refused (409 idempotency_conflict). Use a new key for each new request.
Results
Each assessment's result is its current report's, in a short form of its own:
no_deforestation_found: no forest at the cut-off of 31 December 2020, or forest with no clearing found since.supplier_evidence_needed: a change was found, and the supplier's evidence is needed before you conclude.not_assessed: the plot could not be checked as supplied; itsproblemssay why.
A result names the period it covers, from the cut-off to the last day analysed, and each change found, in the order they happened: its area in hectares, the months it happened between, a point on it and its outline. Where forest could not be seen clearly for long, it says how much (unseen_forest_ha): a limitation the report states, which asks nothing of the supplier. The smallest change we report is 0.3 hectares; every figure we publish on our accuracy is for clearings of 0.5 hectares or more. How we check is on the Methodology page of the app and in each report.
A result is never changed: a later look issues a later report, which replaces it, and the assessment's result is always its current report's. The report's PDF is at pdf_url, with its SHA-256, and its verification page at verify_url.
A result is evidence for your due diligence, not a conclusion on it: the conclusion is yours.
The questions for the supplier, and your conclusion
Where a result asks for the supplier's evidence, the assessment carries the questions for the supplier, one of each kind, each naming the changes it asks about, in the supplier's language with ?lang= (en, fr, es, pt, id, vi), the English beside it. Ask them through your own channels, or have your people send them from the app. A question already answered says answered: by your conclusion on the result, recorded on it or carried from an earlier report, by the supplier's answer to these questions in the app, or by its answer on an earlier report about the same change.
Your conclusion is recorded with POST /v1/assessments/{assessment_id}/conclusion, as a form (multipart/form-data): the version of the result you concluded on (the result's own version), the risk (negligible or non_negligible), its reason, and the evidence it rests on, words (text) and files (JPEG, PNG or PDF, 20 MB each); any other field is refused. A result replaced since you read it, by a later look finding another change say, is refused (409 result_changed, with the version it gives now in details): read it again, and conclude on what it says now. The evidence joins the plot's own, and the conclusion rests on every piece the plot holds then. A negligible risk lets the plot be filed; a non-negligible one keeps it out of your statements. A later conclusion on the same report replaces it, both kept.
A conclusion carries to the plot's next report when that report finds the same change, so a plot checked again is not asked again.
Statements
Draft. POST /v1/statements drafts a statement from your goods, a line for each commodity, each naming the plots it came from by their references:
{"internal_reference_number": "PO-2026-118",
"lines": [{"commodity": "soya", "description": "Soya beans",
"net_weight_kg": "25000", "plot_ids": ["FARM-7", "FARM-9"]}]}
Each plot is filed on its current report, and must be ready to be filed, as GET /v1/plots says in its filing: a plot that is not, one whose result is more than 90 days old or whose outline changed since, say, is named among the statement's errors. The answer is the statement as it will be filed: its plots, its errors, whether it can be filed now and why not, the operator it is filed for, the version of the words it is filed with, and its digest.
File. POST /v1/statements/{statement_id}/file files it through TRACES for your operator, by Panspectra's own TRACES user, which your operator links to itself in TRACES once (the app's filing settings say how; a first link comes with a plan, and one made on a plan keeps working after it ends):
{"digest": "…", "attestation": "2026-10-29b",
"operator_identifier": "…"}
What is filed is exactly what you read: a statement changed since, by a newer report of one of its plots, say, is refused (409 digest_changed) with its new digest, and one whose plot grew too old since it was drafted is refused (409 not_filable). Filing it, your organisation says:
I am authorised to file this statement for [the operator]. I approve it, as shown above, for filing in the EU Information System in [the operator]'s name by Panspectra's TRACES user, which [the operator] authorised in TRACES. By filing it, [the operator] confirms that due diligence in accordance with Regulation (EU) 2023/1115 was carried out and that no or only a negligible risk was found that the relevant products do not comply with Article 3, point (a) or (b), of that Regulation, and it remains responsible for the statement. Panspectra sends the statement as approved.
attestation is the version of these words, 2026-10-29b; if they change, the API says so (409 conflict) until you file with the new version. A statement is sent once, whatever you retry: it answers 202, and 200 when asked again. Its status moves from submitting to submitted, then filed with its reference and verification numbers once TRACES gives them, or refused, TRACES's reasons in its submission_detail. Where TRACES never answered, its submission says unanswered, and nothing settles it: look for it in TRACES, as the email to your people says.
An organisation's keys file at most 100 statements a day (409 ceiling_reached); write to us for more.
While filing through TRACES is not available for your organisation, each statement says so in its why_not and withdraw_why_not, and filing a statement or a correction, or withdrawing one, is refused before anything else is checked (409 filing_not_available): a statement's files, on its page in the app, let you file it by hand in TRACES.
Correct and withdraw. Within its 72 hours a filed statement is corrected by drafting another that names it ("amends": "{statement_id}") and filing that, or withdrawn with POST /v1/statements/{statement_id}/withdraw. A correction is filed as the amendment of the statement standing in its place: the one it names, or the latest correction of it, so that the goods never stand twice in TRACES. Once that statement can no longer be amended, its 72 hours over or it withdrawn, filing the correction is refused (409 not_filable) unless you add "as_new": true, which files it as a new statement, the one it corrects standing beside it unless withdrawn. The statement says how it was filed (filed_as: statement or amendment) and, for an amendment, the statement it replaced (replaces).
Delete. A draft nobody filed is deleted with DELETE /v1/statements/{statement_id}. One filed through TRACES stays in your records.
Webhooks
A webhook tells your systems when something changes, so that they need not ask. An admin makes one in the app, on the organisation's page: its address (https), its name and its events. Its secret is shown once. An address takes one webhook, which may take both events. Webhooks come with a plan as keys do: none is made on pay as you go, those made on a plan keep working after it ends, and a trial has none.
Two events, each naming what changed and its state at the moment it happened. A delivery may come late or out of order, so read the state again from the API before acting on it:
assessment.updated, withassessment_id,plot_id,status,outcomeand areason:reported,replaced,rechecking,restoredorconcluded.statement.updated, withstatement_id,status, its numbers once filed and areason:approved,filed,amended,refused,withdrawn,unansweredorunsettled.
A test sends webhook.test.
Each delivery is a POST of {"type": …, "timestamp": …, "data": {…}}, signed to the Standard Webhooks specification, whose libraries check it in most languages. The headers webhook-id, webhook-timestamp and webhook-signature carry the delivery's id, its time in seconds and v1, with the base64 HMAC-SHA256, under the secret's bytes (the base64 after whsec_), of the id, the time and the body joined by full stops. Check the signature, and that the time is within five minutes; the id is the same on every try, so that a delivery taken twice is seen.
Answer with a 2xx within 15 seconds, counted from our connecting to the status line and headers of your answer; its body is not read. A delivery that fails is tried again after 5 minutes, 30 minutes, 2 hours, 12 hours, a day, two days and two days again. A webhook whose every delivery failed for five days is turned off, and the organisation's admins are emailed. For a day after a new secret is made, deliveries are signed with both; a second new secret made within that day replaces the first new one, and the old one signs until its day ends.
Catching up, pages, limits and errors
Catching up. GET /v1/plots?changed_since=… and GET /v1/statements?changed_since=… answer what changed since a moment of our clock. Each page says when it was read, as_of: keep the first page's, and ask the next changed_since five minutes before it, so that no change is ever missed, whatever your own clock says; an item may come twice, which changes nothing. A plot moves when its result passes its 90 days, the day after its filing.until, as when its result or your conclusion changes.
Pages. A list answers 100 items, up to 1,000 with limit, and the cursor of the next page in next; none on the last. The plots come in the order of their references, the statements newest first.
Limits. An address makes up to 600 requests a minute with a key, and 60 without one. Quotes and sends, each checking up to 20,000 plots, are 5 a minute from an address. Beyond, our load balancer answers 429 Too Many Requests without a body of ours: wait a minute, and try again.
Whether the API is up. GET https://eudr-api.panspectra.com/health answers {"status": "ok"} while the API's service is up, with no key, for a monitor to ask at most once a minute. It looks at nothing behind the service, so a request may still be refused unavailable for a moment: retry it after the seconds its Retry-After names.
Errors. Every refusal has the same form:
{"error": {"code": "invalid", "message": "…",
"fields": [{"field": "lines.0.commodity", "message": "…"}],
"request_id": "req_…"}}
Its code is one of a fixed list: unauthorized (401: no key, or a key revoked), forbidden (403: a viewer's key editing, or a call from an address the key is not limited to), organisation_closing (403: the organisation is being deleted), not_found (404), method_not_allowed (405), invalid (422: the request's form, field by field), conflict (409), consent_needed, being_assessed, assessed_today, not_ready, not_filable, filing_not_available, digest_changed, result_changed, ceiling_reached and idempotency_conflict (409), too_large (413), paused (503, with Retry-After, while the service is shut for maintenance), unavailable (503, with Retry-After: we cannot answer just now) and fault (500: ours, and we are told). What a refusal gives you to act on is in its details: a send's fresh quote, a statement's new digest, the version of the words a statement is filed with, the version of a result. Every answer carries its request's id in the X-Request-Id header: quote it when you write to us.
Versions and changes
The version is in the path, /v1. Within it a change only adds: a route, an optional field of a request, a field of an answer, an event, or a value of a field this guide names as open (a result's problems, a plot's reason not to be filed). Ignore what you do not know. Anything else is a new version, /v2, with /v1 kept a year after it opens, its retiring routes answering with Deprecation and Sunset headers, and their users emailed. Until our first customer integrates, /v1 itself may still change.
Changes
- 2026-11-14: A send leaves out a plot checked that day as it is now (
assessed_today), and one that takes none of the plots it names is refused. While filing through TRACES is not available for your organisation, filing and withdrawing are refused,filing_not_available. - 2026-11-09: A plot larger than 20,000 ha is never checked, its problem
above_maximum_area. Keys and webhooks come with a plan; a trial organisation's keys are refused,403 forbidden. A first link to TRACES comes with a plan too. The limits are counted by address, and quotes and sends have their own, 5 a minute. A plot larger than 150 ha counts once for every 150 ha begun. - 2026-11-07: A conclusion names the result's
version, and its form refuses a field it does not take. Drafting a statement, recording a conclusion and filing take anIdempotency-Key. A correction whose statement can no longer be amended is filed only with"as_new": true, and a statement says how it was filed (filed_as,replaces) and why TRACES refused it (submission_detail). A plot'sfilinggivesuntil, and every pageas_of. A send names the references it does not take. The codesmethod_not_allowed,result_changedandunavailable.GET /health, with no key. A sandbox's reports say so on every page, and its questions to suppliers go to its own people. - 2026-11-06: The first version.
Reference
Plots
Plots sent to be checked, and the organisation's library.
Quote a send
POST /v1/assessments/quote
What sending the plots would use of the plan, creating nothing: each plot as the intake reads it, the plots a send leaves out (those being checked already, and those checked today as they are now), and the plan's figures. Any key.
Body
application/json: Plots
Answers
Example request
{
"plots": {
"features": [
{
"geometry": {
"coordinates": [
[
[
-54.196000000000005,
-10.0
],
[
-54.196000000000005,
-9.996
],
[
-54.2,
-9.996
],
[
-54.2,
-10.0
],
[
-54.196000000000005,
-10.0
]
]
],
"type": "Polygon"
},
"properties": {
"commodity": "soya",
"country": "BR",
"plot_id": "FARM-7",
"supplier": "Coop Norte"
},
"type": "Feature"
},
{
"geometry": {
"coordinates": [
[
[
-54.096000000000004,
-10.0
],
[
-54.096000000000004,
-9.996
],
[
-54.1,
-9.996
],
[
-54.1,
-10.0
],
[
-54.096000000000004,
-10.0
]
]
],
"type": "Polygon"
},
"properties": {
"commodity": "soya",
"country": "BR",
"plot_id": "FARM-9",
"supplier": "Coop Norte"
},
"type": "Feature"
}
],
"type": "FeatureCollection"
}
}Example answer (200)
{
"allowance": {
"basis": "per_plot",
"charge_cents": 0,
"contract_year": 1,
"counted": 2,
"currency": "EUR",
"free": 0,
"granted": 0,
"included": null,
"overage": 0,
"pending_before": 0,
"plan": {
"id": "pay_as_you_go",
"name": "Pay as you go"
},
"plots": 2,
"rejected": 0,
"remaining_after": null,
"remaining_before": null,
"repeated": 0,
"standing": "per_plot",
"unit_price_cents": 0,
"used_after": null,
"used_before": null,
"within": null,
"year_end": "2027-11-07",
"year_start": "2026-11-08"
},
"left_out": [],
"plots": [
{
"notices": [],
"plot_id": "FARM-7",
"problems": [],
"valid": true
},
{
"notices": [],
"plot_id": "FARM-9",
"problems": [],
"valid": true
}
]
}Send plots to be checked
POST /v1/assessments
Each plot sent becomes an assessment of its own, numbered on the plot; a plot named that the send does not take is named in left_out, with why. Plots beyond the plan's allowance need the consent to exactly the figures their quote gave. Safe to retry with an Idempotency-Key. An editor's key.
Parameters
| Field | Type | What it is |
|---|---|---|
Idempotency-Key header, optional | string | Makes a retried send safe: the same key and body answer with the assessments the first made. |
Body
application/json: Send
Answers
200The same request again under its Idempotency-Key: what the first made, nothing sent again. (application/json): Sent201The plots sent. (application/json): Sent- Otherwise a refusal: Error
Example request
{
"plots": {
"features": [
{
"geometry": {
"coordinates": [
[
[
-54.196000000000005,
-10.0
],
[
-54.196000000000005,
-9.996
],
[
-54.2,
-9.996
],
[
-54.2,
-10.0
],
[
-54.196000000000005,
-10.0
]
]
],
"type": "Polygon"
},
"properties": {
"commodity": "soya",
"country": "BR",
"plot_id": "FARM-7",
"supplier": "Coop Norte"
},
"type": "Feature"
},
{
"geometry": {
"coordinates": [
[
[
-54.096000000000004,
-10.0
],
[
-54.096000000000004,
-9.996
],
[
-54.1,
-9.996
],
[
-54.1,
-10.0
],
[
-54.096000000000004,
-10.0
]
]
],
"type": "Polygon"
},
"properties": {
"commodity": "soya",
"country": "BR",
"plot_id": "FARM-9",
"supplier": "Coop Norte"
},
"type": "Feature"
}
],
"type": "FeatureCollection"
}
}Example answer (201)
{
"allowance": {
"basis": "per_plot",
"charge_cents": 0,
"contract_year": 1,
"counted": 2,
"currency": "EUR",
"free": 0,
"granted": 0,
"included": null,
"overage": 0,
"pending_before": 0,
"plan": {
"id": "pay_as_you_go",
"name": "Pay as you go"
},
"plots": 2,
"rejected": 0,
"remaining_after": null,
"remaining_before": null,
"repeated": 0,
"standing": "per_plot",
"unit_price_cents": 0,
"used_after": null,
"used_before": null,
"within": null,
"year_end": "2027-11-07",
"year_start": "2026-11-08"
},
"assessments": [
{
"assessment_id": "asm-000000000004",
"number": 1,
"plot_id": "FARM-7",
"status": "in_progress"
},
{
"assessment_id": "asm-000000000001",
"number": 1,
"plot_id": "FARM-9",
"status": "in_progress"
}
],
"left_out": [],
"plots": [
{
"notices": [],
"plot_id": "FARM-7",
"problems": [],
"valid": true
},
{
"notices": [],
"plot_id": "FARM-9",
"problems": [],
"valid": true
}
]
}List the plots
GET /v1/plots
The organisation's plots in the order of their references, a page at a time; with changed_since, those changed since a moment of our clock: a page's as_of, less a few minutes. Any key.
Parameters
| Field | Type | What it is |
|---|---|---|
status query, optional | not_checked | in_progress | done | not_checked, in_progress or done. |
commodity query, optional | string | The commodity: cattle, cocoa, coffee, oil_palm, rubber, soya or wood. |
country query, optional | string | Two letters, ISO 3166. |
changed_ query, optional | string (date-time) | Only the plots whose status, result, conclusion or filing changed after this moment, by our clock (updated_at): the as_of of the last page read, less a few minutes. |
limit query, optional | integer | How many items a page holds: 100 unless asked, 1,000 at most. |
cursor query, optional | string | The page's next. |
Answers
Example answer (200)
{
"as_of": "2026-11-02T09:00:00+00:00",
"items": [
{
"commodity": "soya",
"conclusion_risk": null,
"country": "BR",
"filing": {
"ready": true,
"until": "2027-01-31",
"why": null
},
"latest": {
"assessment_id": "asm-000000000004",
"period_end": "2026-11-02",
"result": "no_deforestation_found"
},
"number": 1,
"plot_id": "FARM-7",
"status": "done",
"supplier": "Coop Norte",
"updated_at": "2026-11-02T09:00:00+00:00"
},
{
"commodity": "soya",
"conclusion_risk": "negligible",
"country": "BR",
"filing": {
"ready": true,
"until": "2027-01-31",
"why": null
},
"latest": {
"assessment_id": "asm-000000000001",
"period_end": "2026-11-02",
"result": "supplier_evidence_needed"
},
"number": 2,
"plot_id": "FARM-9",
"status": "done",
"supplier": "Coop Norte",
"updated_at": "2026-11-02T09:00:00+00:00"
}
],
"next": null
}Read a plot
GET /v1/plots/{plot_id}
A plot: its latest assessment that stands, the organisation's conclusion, and whether a statement may file it now. Any key.
Parameters
| Field | Type | What it is |
|---|---|---|
plot_ path | string | The plot, by the organisation's reference. |
Answers
Example answer (200)
{
"commodity": "soya",
"conclusion_risk": "negligible",
"country": "BR",
"filing": {
"ready": true,
"until": "2027-01-31",
"why": null
},
"latest": {
"assessment_id": "asm-000000000001",
"period_end": "2026-11-02",
"result": "supplier_evidence_needed"
},
"number": 2,
"plot_id": "FARM-9",
"status": "done",
"supplier": "Coop Norte",
"updated_at": "2026-11-02T09:00:00+00:00"
}Assessments
Each send of a plot: its result, its questions for the supplier, and the organisation's conclusion.
Read an assessment
GET /v1/assessments/{assessment_id}
An assessment: its status, its current report's result, the questions it leaves for the supplier in the language asked for, and the organisation's conclusion. Any key.
Parameters
| Field | Type | What it is |
|---|---|---|
assessment_ path | string | The assessment. |
lang query, optional | en | fr | es | pt | id | vi | The supplier's language for the questions; English by default. |
Answers
200Done. (application/json): Assessment- Otherwise a refusal: Error
Example answer (200)
{
"assessment_id": "asm-000000000001",
"conclusion": null,
"number": 1,
"pdf_sha256": "8ee89711330c1ccf39a2e65ad12bbd7df4a4a2ee857f53b4823f00fecb7bd252",
"pdf_url": "https://eudr-api.panspectra.com/v1/assessments/asm-000000000001/pdf",
"plot_id": "FARM-9",
"questions": [
{
"answered": false,
"ask": "What happened to this ground, and has it been used for agriculture since?",
"code": "explain_clearing",
"english": null,
"events": [
1
],
"settles": "Evidence that it is growing back with no farming over two seasons; of a use other than farming that explains the whole area, such as a road, a reservoir or buildings; or a planting record showing that the trees there were a crop planted before 2021."
}
],
"result": {
"assessed_at": "2026-11-02T09:00:00+00:00",
"assessment": 1,
"changed_area_ha": 3.61,
"changes": [
{
"area_ha": 3.61,
"centre": [
-54.098018,
-9.997944
],
"cleared_from": "2023-02",
"cleared_to": "2023-03",
"number": 1,
"outline": {
"coordinates": [
[
[
-54.0971591,
-9.9970785
],
[
-54.0988905,
-9.9970936
],
[
-54.0988753,
-9.9988099
],
[
-54.0971439,
-9.9987948
],
[
-54.0971591,
-9.9970785
]
]
],
"type": "Polygon"
}
}
],
"period_end": "2026-11-02",
"period_start": "2020-12-31",
"plot_id": "FARM-9",
"problems": [],
"result": "supplier_evidence_needed",
"schema_version": "1.0",
"unseen_forest_ha": null,
"verification_code": "0e8f7f17837b6871",
"version": 1
},
"sent_at": "2026-11-02T09:00:00+00:00",
"status": "done",
"updated_at": "2026-11-02T09:00:00+00:00",
"verify_url": "https://panspectra.com/eudr/verify/0e8f7f17837b6871"
}Download its report
GET /v1/assessments/{assessment_id}/pdf
The assessment's current report, as a PDF. Any key.
Parameters
| Field | Type | What it is |
|---|---|---|
assessment_ path | string | The assessment. |
Answers
200Done. (application/pdf)- Otherwise a refusal: Error
Record a conclusion
POST /v1/assessments/{assessment_id}/conclusion
The organisation's conclusion on a result that asked for the supplier's evidence, with the evidence it rests on, as a form (multipart/form-data), made on the result's version it names: one replaced since is refused, result_changed. A later one on the same report replaces it, both kept. Safe to retry with an Idempotency-Key. An editor's key.
Parameters
| Field | Type | What it is |
|---|---|---|
assessment_ path | string | The assessment. |
Idempotency-Key header, optional | string | Makes a retried request safe: the same key and request answer what the first made (200), making nothing again; another request under the key is refused (idempotency_conflict). |
Body
multipart/form-data: ConclusionForm
Answers
200The same request again under its Idempotency-Key: the assessment as it stands, nothing recorded again. (application/json): Assessment201The conclusion recorded: the assessment, with it. (application/json): Assessment- Otherwise a refusal: Error
Example request
{
"reason": "The cleared land is a fallow the supplier replanted with soya before 2020, as its photographs show.",
"risk": "negligible",
"text": "The supplier's answer of 12 October: the fallow was replanted in 2019.",
"version": "1"
}Example answer (201)
{
"assessment_id": "asm-000000000001",
"conclusion": {
"carried": false,
"evidence": [
{
"files": [],
"received_at": "2026-11-02T09:00:00+00:00",
"source": "customer",
"text": "The supplier's answer of 12 October: the fallow was replanted in 2019."
}
],
"reason": "The cleared land is a fallow the supplier replanted with soya before 2020, as its photographs show.",
"recorded_at": "2026-11-02T09:00:00+00:00",
"recorded_by": "the API key “initial” (key-000000000002)",
"risk": "negligible"
},
"number": 1,
"pdf_sha256": "8ee89711330c1ccf39a2e65ad12bbd7df4a4a2ee857f53b4823f00fecb7bd252",
"pdf_url": "https://eudr-api.panspectra.com/v1/assessments/asm-000000000001/pdf",
"plot_id": "FARM-9",
"questions": [
{
"answered": true,
"ask": "What happened to this ground, and has it been used for agriculture since?",
"code": "explain_clearing",
"english": null,
"events": [
1
],
"settles": "Evidence that it is growing back with no farming over two seasons; of a use other than farming that explains the whole area, such as a road, a reservoir or buildings; or a planting record showing that the trees there were a crop planted before 2021."
}
],
"result": {
"assessed_at": "2026-11-02T09:00:00+00:00",
"assessment": 1,
"changed_area_ha": 3.61,
"changes": [
{
"area_ha": 3.61,
"centre": [
-54.098018,
-9.997944
],
"cleared_from": "2023-02",
"cleared_to": "2023-03",
"number": 1,
"outline": {
"coordinates": [
[
[
-54.0971591,
-9.9970785
],
[
-54.0988905,
-9.9970936
],
[
-54.0988753,
-9.9988099
],
[
-54.0971439,
-9.9987948
],
[
-54.0971591,
-9.9970785
]
]
],
"type": "Polygon"
}
}
],
"period_end": "2026-11-02",
"period_start": "2020-12-31",
"plot_id": "FARM-9",
"problems": [],
"result": "supplier_evidence_needed",
"schema_version": "1.0",
"unseen_forest_ha": null,
"verification_code": "0e8f7f17837b6871",
"version": 1
},
"sent_at": "2026-11-02T09:00:00+00:00",
"status": "done",
"updated_at": "2026-11-02T09:00:00+00:00",
"verify_url": "https://panspectra.com/eudr/verify/0e8f7f17837b6871"
}Statements
Due diligence statements, from a draft to their numbers.
Draft a statement
POST /v1/statements
A statement drafted from goods and the plots they came from, each plot filed on its current report, a plot not ready to be filed named among its errors; a correction names the statement it corrects. Safe to retry with an Idempotency-Key. An editor's key.
Parameters
| Field | Type | What it is |
|---|---|---|
Idempotency-Key header, optional | string | Makes a retried request safe: the same key and request answer what the first made (200), making nothing again; another request under the key is refused (idempotency_conflict). |
Body
application/json: StatementDraft
Answers
200The same request again under its Idempotency-Key: the statement the first drafted, as it stands. (application/json): Statement201The statement drafted. (application/json): Statement- Otherwise a refusal: Error
Example request
{
"internal_reference_number": "PO-2026-118",
"lines": [
{
"commodity": "soya",
"description": "Soya beans",
"net_weight_kg": "25000",
"plot_ids": [
"FARM-7",
"FARM-9"
]
}
]
}Example answer (201)
{
"amends": null,
"attestation": "2026-10-29b",
"can_file": true,
"can_withdraw": false,
"change_until": null,
"created_at": "2026-11-02T09:00:00+00:00",
"digest": "553295e4b848bee781c30a0c86a5b731330806eaaca214de195e48761b8a61ee",
"errors": [],
"filed_as": null,
"filed_at": null,
"internal_reference_number": "PO-2026-118",
"operator_identifier": "SANDBOX",
"operator_name": "Importer GmbH",
"plots": [
"FARM-7",
"FARM-9"
],
"reference_number": null,
"replaces": null,
"statement_id": "dft-000000000003",
"status": "draft",
"submission": null,
"submission_detail": null,
"updated_at": "2026-11-02T09:00:00+00:00",
"verification_number": null,
"why_not": null,
"withdraw_why_not": "Only a filed statement is withdrawn."
}List the statements
GET /v1/statements
The organisation's statements, the newest first, a page at a time; with changed_since, those changed since a moment of our clock: a page's as_of, less a few minutes. Any key.
Parameters
| Field | Type | What it is |
|---|---|---|
changed_ query, optional | string (date-time) | Only the statements changed after this moment, by our clock (updated_at): the as_of of the last page read, less a few minutes. |
limit query, optional | integer | How many items a page holds: 100 unless asked, 1,000 at most. |
cursor query, optional | string | The page's next. |
Answers
200Done. (application/json): StatementPage- Otherwise a refusal: Error
Example answer (200)
{
"as_of": "2026-11-02T09:00:00+00:00",
"items": [
{
"created_at": "2026-11-02T09:00:00+00:00",
"digest": "553295e4b848bee781c30a0c86a5b731330806eaaca214de195e48761b8a61ee",
"filed_at": null,
"internal_reference_number": "PO-2026-118",
"reference_number": null,
"statement_id": "dft-000000000003",
"status": "draft",
"submission": null,
"updated_at": "2026-11-02T09:00:00+00:00",
"verification_number": null
}
],
"next": null
}Read a statement
GET /v1/statements/{statement_id}
A statement as it will be or was filed: its digest, its plots, why it cannot be filed now where not, the operator and the words it is filed with, and its numbers once filed. Any key.
Parameters
| Field | Type | What it is |
|---|---|---|
statement_ path | string | The statement. |
Answers
Example answer (200)
{
"amends": null,
"attestation": "2026-10-29b",
"can_file": true,
"can_withdraw": false,
"change_until": null,
"created_at": "2026-11-02T09:00:00+00:00",
"digest": "553295e4b848bee781c30a0c86a5b731330806eaaca214de195e48761b8a61ee",
"errors": [],
"filed_as": null,
"filed_at": null,
"internal_reference_number": "PO-2026-118",
"operator_identifier": "SANDBOX",
"operator_name": "Importer GmbH",
"plots": [
"FARM-7",
"FARM-9"
],
"reference_number": null,
"replaces": null,
"statement_id": "dft-000000000003",
"status": "draft",
"submission": null,
"submission_detail": null,
"updated_at": "2026-11-02T09:00:00+00:00",
"verification_number": null,
"why_not": null,
"withdraw_why_not": "Only a filed statement is withdrawn."
}Delete a draft
DELETE /v1/statements/{statement_id}
A draft nobody filed. One filed through TRACES stays in the records. An editor's key.
Parameters
| Field | Type | What it is |
|---|---|---|
statement_ path | string | The statement. |
Answers
204Done.- Otherwise a refusal: Error
File a statement
POST /v1/statements/{statement_id}/file
Files exactly the statement read, by its digest, through TRACES for the operator it names, once whatever is retried. A correction is filed as the amendment of the statement standing in its place, or as a new statement where as_new asks, once that one can no longer be amended. Its numbers come back when TRACES gives them. An editor's key.
Parameters
| Field | Type | What it is |
|---|---|---|
statement_ path | string | The statement. |
Idempotency-Key header, optional | string | Makes a retried filing safe: the same key and request answer the statement again (200), whatever has become of it since, and file nothing; another request under the key is refused (idempotency_conflict). |
Body
application/json: FileStatement
Answers
200Asked again: the statement as it stands, nothing sent again. (application/json): Statement202Taken: sent to TRACES within the minute. (application/json): Statement- Otherwise a refusal: Error
Example request
{
"attestation": "2026-10-29b",
"digest": "553295e4b848bee781c30a0c86a5b731330806eaaca214de195e48761b8a61ee",
"operator_identifier": "SANDBOX"
}Example answer (202)
{
"amends": null,
"attestation": "2026-10-29b",
"can_file": false,
"can_withdraw": true,
"change_until": "2026-11-05T08:50:00+00:00",
"created_at": "2026-11-02T09:00:00+00:00",
"digest": "553295e4b848bee781c30a0c86a5b731330806eaaca214de195e48761b8a61ee",
"errors": [],
"filed_as": "statement",
"filed_at": "2026-11-02T09:00:00+00:00",
"internal_reference_number": "PO-2026-118",
"operator_identifier": "SANDBOX",
"operator_name": "Importer GmbH",
"plots": [
"FARM-7",
"FARM-9"
],
"reference_number": "SANDBOX-000001",
"replaces": null,
"statement_id": "dft-000000000003",
"status": "filed",
"submission": "available",
"submission_detail": null,
"updated_at": "2026-11-02T09:00:00+00:00",
"verification_number": "SB00000002",
"why_not": "This statement was filed.",
"withdraw_why_not": null
}Withdraw a statement
POST /v1/statements/{statement_id}/withdraw
Withdraws a filed statement from TRACES, within its 72 hours. An editor's key.
Parameters
| Field | Type | What it is |
|---|---|---|
statement_ path | string | The statement. |
Answers
200Done. (application/json): Statement202Taken: its withdrawal is sent to TRACES within the minute. (application/json): Statement- Otherwise a refusal: Error
Example answer (202)
{
"amends": null,
"attestation": "2026-10-29b",
"can_file": false,
"can_withdraw": false,
"change_until": null,
"created_at": "2026-11-02T09:00:00+00:00",
"digest": "553295e4b848bee781c30a0c86a5b731330806eaaca214de195e48761b8a61ee",
"errors": [],
"filed_as": "statement",
"filed_at": "2026-11-02T09:00:00+00:00",
"internal_reference_number": "PO-2026-118",
"operator_identifier": "SANDBOX",
"operator_name": "Importer GmbH",
"plots": [
"FARM-7",
"FARM-9"
],
"reference_number": "SANDBOX-000001",
"replaces": null,
"statement_id": "dft-000000000003",
"status": "withdrawn",
"submission": "withdrawn",
"submission_detail": null,
"updated_at": "2026-11-02T09:00:00+00:00",
"verification_number": "SB00000002",
"why_not": "This statement was filed.",
"withdraw_why_not": "Only a filed statement is withdrawn."
}Health
Whether the API is up, for a monitor to watch.
Whether the API is up
GET /health
Whether the API's service is up, and nothing else. It looks at nothing behind the service, so a request may still be refused unavailable for a moment. Ask it at most once a minute. No key.
Answers
200The API's service is up. (application/json): Health
Example answer (200)
{
"status": "ok"
}Webhook events
assessment.updated
An assessment's result was reported, replaced, taken back to be checked again or restored, or the organisation's conclusion was recorded.
Its delivery: AssessmentEvent
Example delivery
{
"data": {
"assessment_id": "asm-000000000004",
"outcome": "no_deforestation_found",
"plot_id": "FARM-7",
"reason": "reported",
"status": "done"
},
"timestamp": "2026-11-02T09:00:00+00:00",
"type": "assessment.updated"
}statement.updated
A statement was approved to be filed, filed, filed as a correction, refused, withdrawn, or never answered by TRACES.
Its delivery: StatementEvent
Example delivery
{
"data": {
"reason": "filed",
"reference_number": "SANDBOX-000001",
"statement_id": "dft-000000000003",
"status": "filed",
"verification_number": "SB00000002"
},
"timestamp": "2026-11-02T09:00:00+00:00",
"type": "statement.updated"
}Models
ActivityType
One of IMPORT | EXPORT | DOMESTIC.
Allowance
What the plots will use of the plan's allowance this contract year: each plot counts as its first report is issued, so a plot whose check is not completed is never counted. Every figure but the plots named, those refused and those counted already is in plots as counted: a plot larger than 150 ha counts once for every 150 ha begun, an outline by its measured area, a point by the area it declares (4 ha when it declares none), and stays one plot.
| Field | Type | What it is |
|---|---|---|
plan | PlanRef | |
basis | string | |
contract_ | integer | |
year_ | string (date) | |
year_ | string (date) | |
plots | integer | The plots named. |
rejected | integer | Those the intake refused, never counted. |
repeated | integer | Those counted already within the last 12 months. |
counted | integer | What those that count count as, each as its first report is issued: a plot larger than 150 ha once for every 150 ha begun. |
included optional | integer | The year's allowance: the plan's plots and any granted. |
granted optional | integer | The plots granted for the contract year. |
used_ optional | integer | The plots counted this contract year before. |
pending_ optional | integer | The plots being checked before, which count as their reports are issued. |
remaining_ optional | integer | |
within optional | integer | |
overage | integer | Those beyond the allowance, billed. |
free optional | integer | On a plan without an allowance, those the year's granted plots pay for. |
used_ optional | integer | |
remaining_ optional | integer | |
currency optional | string | |
unit_ optional | integer | |
charge_ optional | integer | |
standing | string |
Assessment
A plot's assessment: one send of the plot, numbered on it.
| Field | Type | What it is |
|---|---|---|
assessment_ | string | |
plot_ | string | The plot, by the organisation's reference. |
number | integer | The assessment's number on the plot. |
status | in_progress | done | in_progress until its result issues, and while it is checked again; done once its result stands. |
sent_ | string (date-time) | |
result optional | ReportResult | The result of its current report, once issued. |
questions optional | list of Question | What the result leaves for the supplier; empty where it asks nothing. |
conclusion optional | Conclusion | The organisation's conclusion on the current report, recorded on it or carried to it. |
pdf_ optional | string | The report, as a PDF. |
pdf_ optional | string | The PDF's SHA-256. |
verify_ optional | string | The verification page anyone may open to check the report. |
updated_ | string (date-time) |
AssessmentEvent
A delivery of assessment.updated.
| Field | Type | What it is |
|---|---|---|
type | assessment.updated | |
timestamp | string (date-time) | When it happened. |
data | AssessmentUpdated |
AssessmentUpdated
What changed of an assessment, as a webhook tells it: what happened, and its state at that moment, which a later change may have moved on; a receiver reads the assessment again from the API before acting on it.
| Field | Type | What it is |
|---|---|---|
assessment_ | string | |
plot_ | string | The plot, by the organisation's reference. |
reason | reported | replaced | rechecking | restored | concluded | What happened: its result reported, replaced by a later report, being checked again, back as it was, or the organisation's conclusion recorded. |
status | in_progress | done | |
outcome optional | string | Its result's outcome, while it is done. |
Commodity
The Regulation's seven relevant commodities; a plot declares one.
One of cattle | cocoa | coffee | oil_palm | rubber | soya | wood.
Conclusion
The customer's own conclusion on a report that asked for the supplier's evidence: its assessment of the risk, never a word on our result.
| Field | Type | What it is |
|---|---|---|
risk | negligible | non_negligible | The organisation's assessment of the risk. |
reason | string | Its reason, in its words. |
evidence optional | list of EvidencePiece | The pieces of evidence it rests on. |
recorded_ | string (date-time) | |
recorded_ | string | Who recorded it: a person's address, or the API key by its label. |
carried optional | boolean | Whether it was recorded on an earlier report of the plot and carries to this one, for the same change. |
ConclusionForm
A conclusion, as a form (multipart/form-data).
| Field | Type | What it is |
|---|---|---|
version | integer | The version of the result the conclusion was made on, as the assessment's result gave it (result.version): refused, result_changed, where the assessment's result is another now. |
risk | negligible | non_negligible | The organisation's assessment of the risk. |
reason | string | Its reason. |
text optional | string | The evidence's words: the supplier's answer, say. |
files optional | list of string | The evidence's files: JPEG, PNG or PDF, 20 MB each. |
Consent
The consent to what plots beyond the plan's allowance add to the invoice, exactly as the quote said it.
| Field | Type | What it is |
|---|---|---|
overage_ | integer | The plots beyond the allowance. |
charge_ optional | integer | Their amount, in cents; none while unset. |
Error
A refusal.
| Field | Type | What it is |
|---|---|---|
error | ErrorDetail |
ErrorDetail
| Field | Type | What it is |
|---|---|---|
code | string | What went wrong, from a fixed list: unauthorized, forbidden, organisation_closing, not_found, method_not_allowed, invalid, conflict, consent_needed, being_assessed, assessed_today, not_ready, not_filable, filing_not_available, digest_changed, result_changed, ceiling_reached, idempotency_conflict, too_large, rate_limited, paused, unavailable, fault. |
message | string | What went wrong, in words. |
fields optional | list of Problem | Each field refused, for a request not in the form it takes. |
details optional | object | What a refusal gives to act on, where it gives anything: a send's fresh quote (consent_needed), a statement's new digest (digest_changed), the version of the words a statement is filed with (conflict), the version of the result now (result_changed). |
request_ | string | The request's id, also in the X-Request-Id header, to quote to us. |
EvidenceFile
| Field | Type | What it is |
|---|---|---|
name | string | The file's name as it was added. |
size_ | integer | Its size, in bytes. |
sha256 | string | Its content's SHA-256. |
EvidencePiece
A piece of the plot's evidence a conclusion rests on.
| Field | Type | What it is |
|---|---|---|
text optional | string | Its words, if any. |
files optional | list of EvidenceFile | |
source | string | Where it came from: the organisation's own, or the supplier's answer. |
received_ | string (date-time) | When it reached the organisation. |
FileStatement
A statement filed through TRACES, exactly as it was read.
| Field | Type | What it is |
|---|---|---|
digest | string | The statement's digest as its answer gave it: what is filed is exactly what was read. |
attestation | string | The version of the words the organisation files with, as the statement's answer and the guide give them. |
operator_ | string | The operator it is filed for, as the statement's answer named it. |
as_ optional | boolean | For a correction (amends) whose statement can no longer be amended, its 72 hours over or the statement withdrawn: file it as a new statement. Without it such a correction is refused, so that the same goods never stand twice in TRACES unawares. |
Filing
Whether a statement may file the plot now.
| Field | Type | What it is |
|---|---|---|
ready | boolean | |
why optional | string | Why not, where not: not_checked, being_checked, too_old, outline_changed, conclusion_needed, not_negligible or to_correct. |
until optional | string (date) | The last day a statement files the plot on its latest result: 90 days after the last day the result covers. After it the plot is too_old until it is checked again. None for a plot without a result. |
Finding
An outcome: no_deforestation_found, supplier_evidence_needed or not_assessed; in_progress while an assessment's result is not out.
One of no_deforestation_found | supplier_evidence_needed | not_assessed | in_progress.
GeoJSONGeometry
A GeoJSON geometry in WGS-84 (longitude, latitude).
| Field | Type | What it is |
|---|---|---|
type | string | The GeoJSON geometry type; a plot is a Point, Polygon or MultiPolygon. |
coordinates | any | Longitude, latitude pairs in degrees, nested as the type requires; always lists, so a record round-trips through JSON unchanged. |
Health
Whether the API is up.
| Field | Type | What it is |
|---|---|---|
status | ok | The API's service is up. It looks at nothing behind the service, so a request may still be refused unavailable for a moment. |
Intake
A plot as the intake read it: whether it can be assessed as supplied, why not, and what was mended.
| Field | Type | What it is |
|---|---|---|
plot_ | string | |
valid | boolean | |
problems optional | list of IntakeProblem | |
notices optional | list of string |
IntakeProblem
| Field | Type | What it is |
|---|---|---|
code | string | |
message | string |
Latest
| Field | Type | What it is |
|---|---|---|
assessment_ | string | |
result optional | string | Its outcome, once issued. |
period_ optional | string (date) |
LeftOut
A plot named and not sent, and why.
| Field | Type | What it is |
|---|---|---|
plot_ | string | |
why | being_assessed | assessed_today | unknown | retired | invalid | beyond_pilot | being_assessed: it is being checked already; assessed_today: it was checked today as it is now, and its result stands until the next day or until the plot changes; unknown: the library holds no plot of that reference; retired: it was retired from the library; invalid: the library holds it as one that cannot be checked as supplied, to correct first; beyond_pilot: a paid pilot's plots are used, and it does not fit in what is left of them. |
Operator
| Field | Type | What it is |
|---|---|---|
name | string | |
identifier_ optional | EORI | VAT | GLN | TIN | OTHER | |
identifier_ optional | string | |
country optional | string | |
street optional | string | |
postal_ optional | string | |
city optional | string | |
email optional | string | |
phone optional | string |
PlanRef
| Field | Type | What it is |
|---|---|---|
id | string | |
name | string |
Plot
A plot of the organisation's library.
| Field | Type | What it is |
|---|---|---|
plot_ | string | The plot, by the organisation's reference. |
number | integer | The plot's number in the organisation. |
supplier optional | string | Its supplier, as the library names it. |
commodity optional | string | Its commodity: cattle, cocoa, coffee, oil_palm, rubber, soya or wood. |
country optional | string | Its country of production: two letters, ISO 3166. |
status | not_checked | in_progress | done | not_checked, in_progress, or done for a plot whose latest result stands. |
latest optional | Latest | Its latest assessment that stands. |
conclusion_ optional | negligible | non_negligible | The organisation's conclusion on its latest report, where it recorded one or one carried to it. |
filing | Filing | |
updated_ | string (date-time) | When its status, result, conclusion or filing last changed, which changed_since reads: a result passing its 90 days among them, from the day after filing.until. |
PlotPage
A page of the organisation's plots, in the order of their references.
| Field | Type | What it is |
|---|---|---|
items | list of Plot | |
next optional | string | The cursor of the next page; none on the last. |
as_ | string (date-time) | When the page was read, by our clock: ask the next changed_since a few minutes before it, since a change is stamped as it is made and may be read a moment after. |
Plots
The plots of a quote or a send: GeoJSON, or the references of plots the library holds, to check them again.
| Field | Type | What it is |
|---|---|---|
plots optional | object | A GeoJSON FeatureCollection, each feature naming its plot_id, supplier, country and commodity in its properties. |
plot_ optional | list of string | Or the references of plots the library holds. |
Problem
| Field | Type | What it is |
|---|---|---|
field | string | The field refused, by its path in the request. |
message | string | Why, in words. |
Question
A question the result leaves for the supplier, as the supplier's page and paper put it.
| Field | Type | What it is |
|---|---|---|
code | string | The question's kind: clearing_date, forest_at_2020, explain_clearing or explain_disturbance, of a change found; other_changes, of the smaller changes beyond a result's ten largest, asked of together; or correct, for a plot that could not be assessed as supplied. |
events optional | list of integer | The changes it asks of, by their numbers on the plot, as the result's changes number them; none for a correction. |
ask | string | The question, in the language asked for. |
settles | string | What would settle it, in the language asked for. |
english optional | object | The question and what would settle it in English, beside a translation. |
answered | boolean | Whether it is answered already: by the organisation's conclusion on the result, recorded on it or carried from an earlier report, or by the supplier's answer, to this result's questions or to an earlier report's about the same change. |
Quoted
What sending the plots would use, creating nothing.
| Field | Type | What it is |
|---|---|---|
allowance | Allowance | |
left_ | list of LeftOut | |
plots | list of Intake |
ReportChange
A change the report found in the plot's forest.
| Field | Type | What it is |
|---|---|---|
number | integer | Its number on the plot, as the report numbers it. |
area_ | number | Its area, in hectares. |
cleared_ | string | The months it happened between, "YYYY-MM". |
cleared_ | string | |
centre | list of any | A point on it, its largest part's: longitude and latitude. |
outline | GeoJSONGeometry | Its outline. |
ReportResult
A plot report's result, as a customer's systems read it.
| Field | Type | What it is |
|---|---|---|
schema_ optional | 1.0 | |
plot_ | string | The plot, by the customer's own reference. |
assessment | integer | The plot's assessment, numbered on the plot, and the report's version in it: 1 the first, a later one replacing it. |
version | integer | |
verification_ | string | The report's verification code, which finds and checks it. |
assessed_ | string (date-time) | When the assessment was finished. |
period_ optional | string (date) | The period the result covers: from the cut-off to the last day analysed; None when the plot was not assessed. |
period_ optional | string (date) | |
result | Finding | The outcome: no_deforestation_found, supplier_evidence_needed or not_assessed. |
changes optional | list of ReportChange | Each change found, in the order they happened. |
changed_ optional | number | The changes' area together, in hectares. |
unseen_ optional | number | The forest that could not be seen clearly for long stretches since the cut-off, or too seldom before it, in hectares: the limitation the report states of it, which asks nothing of the supplier; None where none went unseen. |
problems optional | list of string | Why the plot could not be assessed as supplied, by code; empty on a plot that was assessed. |
trial optional | boolean | Whether the report was made in a free trial: on real observations, to show how Panspectra works, and not for due diligence. |
Send
| Field | Type | What it is |
|---|---|---|
plots optional | object | A GeoJSON FeatureCollection, each feature naming its plot_id, supplier, country and commodity in its properties. |
plot_ optional | list of string | Or the references of plots the library holds. |
consent optional | Consent | Needed where the plots go beyond the plan's allowance. |
Sent
The plots sent: an assessment of each, the plots left out because they are being assessed, the allowance's figures, and each plot as the intake read it.
| Field | Type | What it is |
|---|---|---|
assessments | list of SentAssessment | |
left_ optional | list of LeftOut | |
allowance optional | Allowance | |
plots optional | list of Intake |
SentAssessment
| Field | Type | What it is |
|---|---|---|
assessment_ | string | |
plot_ | string | |
number | integer | |
status | in_progress | done |
Statement
A statement as it will be, or was, filed.
| Field | Type | What it is |
|---|---|---|
statement_ | string | |
status | string | draft, submitting, submitted, filed, refused, rejected, withdrawing, withdrawn or amended. |
internal_ optional | string | |
digest optional | string | Its SHA-256, which filing it binds. |
reference_ optional | string | |
verification_ optional | string | |
filed_ optional | string (date-time) | |
submission optional | string | Where its latest sending to TRACES stands, where it was approved for TRACES: queued, sending, submitted, available, refused, rejected, not_sent, withdrawn, amended, unanswered (TRACES never answered: look for it there, it is never sent again) or unsettled (TRACES took it and had not settled it a week later). |
created_ | string (date-time) | |
updated_ | string (date-time) | |
plots optional | list of string | Its plots, by their references. |
errors optional | list of string | Why it cannot be filed as it is. |
can_ | boolean | Whether it can be filed now, by an editor's key. |
why_ optional | string | Why it cannot be filed now, where not. |
operator_ optional | string | The operator it is filed for: the one it was approved for once approved, else the organisation's connected operator. |
operator_ optional | string | |
attestation optional | string | The version of the words it is filed with, for FileStatement. |
can_ optional | boolean | |
withdraw_ optional | string | |
change_ optional | string (date-time) | When its 72 hours to correct or withdraw end. |
amends optional | string | The statement it corrects, by its id. |
filed_ optional | statement | amendment | How it was approved to be filed: as a statement of its own, or as the amendment of the statement it replaces in TRACES (replaces); none before. |
replaces optional | string | The statement an amendment replaces in TRACES, by its id: the one it corrects, or the latest correction of it that stands. |
submission_ optional | string | Why its latest sending was refused or rejected, in TRACES's reasons, or why nothing was sent, in words. |
StatementDraft
A statement drafted from goods and plots, as the app's form drafts one: each line's plots filed on their current reports.
| Field | Type | What it is |
|---|---|---|
lines | list of StatementLine | |
production_ optional | string (date) | |
operator optional | Operator | |
activity_ optional | ActivityType | |
country_ optional | string | |
border_ optional | string | |
internal_ optional | string | |
comment optional | string | |
geolocation_ optional | boolean | |
again_ optional | string | |
amends optional | string |
StatementEvent
A delivery of statement.updated.
| Field | Type | What it is |
|---|---|---|
type | statement.updated | |
timestamp | string (date-time) | When it happened. |
data | StatementUpdated |
StatementLine
A line of goods: its commodity and HS heading, its description and quantities, and the plots it came from, by their references.
| Field | Type | What it is |
|---|---|---|
commodity | Commodity | |
hs_ optional | string | |
description | string | |
net_ optional | number or string | |
supplementary_ optional | number or string | |
supplementary_ optional | string | |
percentage_ optional | number or string | |
species_ optional | string | |
species_ optional | string | |
plot_ optional | list of string |
StatementPage
A page of the organisation's statements, the newest first.
| Field | Type | What it is |
|---|---|---|
items | list of StatementSummary | |
next optional | string | |
as_ | string (date-time) | When the page was read, by our clock: ask the next changed_since a few minutes before it, since a change is stamped as it is made and may be read a moment after. |
StatementSummary
A statement as the list gives it.
| Field | Type | What it is |
|---|---|---|
statement_ | string | |
status | string | draft, submitting, submitted, filed, refused, rejected, withdrawing, withdrawn or amended. |
internal_ optional | string | |
digest optional | string | Its SHA-256, which filing it binds. |
reference_ optional | string | |
verification_ optional | string | |
filed_ optional | string (date-time) | |
submission optional | string | Where its latest sending to TRACES stands, where it was approved for TRACES: queued, sending, submitted, available, refused, rejected, not_sent, withdrawn, amended, unanswered (TRACES never answered: look for it there, it is never sent again) or unsettled (TRACES took it and had not settled it a week later). |
created_ | string (date-time) | |
updated_ | string (date-time) |
StatementUpdated
What changed of a statement, as a webhook tells it: what happened, and its state at that moment; the statement read again from the API says where it stands now.
| Field | Type | What it is |
|---|---|---|
statement_ | string | |
reason | approved | filed | amended | refused | withdrawn | unanswered | unsettled | What happened: approved to be filed, filed, filed as a correction, refused by TRACES, withdrawn, or never answered by TRACES. |
status optional | string | Its status now. |
reference_ optional | string | |
verification_ optional | string |