Guides by flow
Events and detection
Query events, request the damage footprint, read the severity.
Fuente del diagrama (mermaid)
sequenceDiagram
participant C as Cliente
participant S as SBOX
C->>S: GET /v1/events?peril=hail
S-->>C: 200 · eventos que tocaron la cartera
C->>S: POST /v1/jobs (geo.damage_footprint)
S-->>C: 202 · job encolado, Location: /v1/jobs/{id}
C->>S: GET /v1/jobs/{id}
S-->>C: 200 · succeeded, resultUrl
C->>S: GET /v1/jobs/{id}/result
S-->>C: 200 · geometría, ha dañadas, celdas por severidad
Why the footprint is asynchronous
A raster query over a plot takes seconds to minutes. Inside the request, the handler dies on timeout, the client retries, and every retry spends again — on Earth Engine those are billable EECUs. That is why the request enqueues and the worker has its own time budget.
Idempotency is decided before touching the provider. A double click costs once.
curl -sS "$SBOX/v1/detections" -H "authorization: Bearer $TOKEN"
curl -sS "$SBOX/v1/events?severity=high" -H "authorization: Bearer $TOKEN"What breaks
402withcost_cap_exceeded: the estimated computation exceeds the organization's budget. It stops before executing, because stopping after spending is not stopping.422 peril_not_supported: that peril has no detection method yet.- A job in a terminal state is never rewritten. Recomputing is a new job: a job's result is evidence, and evidence is not rewritten.