01 Upload Facility Assets
โถStep 1: Upload facility geometry โ with a tag
Mint a signed upload URL and ship the facility bytes. The docs UI's
Upload tab (or any SDK) PUTs the file off meta.client_actions[0].
The upload MUST carry a tags array. This is the contract of this
workflow: the tag is the key step 05 selects on. The tag is applied to
the asset_task at create time and propagates to the resolved plots
beneath the facility (facility โ shed โ plot), so it can be used as the
audit-record filter later.
โถRequest
POST /ingestions/assets with Content-Type: application/json
| Field | Required | Notes |
|---|---|---|
location_type | Yes | facility for this workflow |
commodity_type | Yes | e.g. coffee |
tags | Yes (here) | One or more free-form strings (โค100 chars). The workflow's selection key โ used by step 05's filter.tag. |
metrics | No | Omit here โ deforestation is triggered in step 3 |
โถResponse (201)
data.idโ captured into{{fac_task_id}}, used by steps 2, 3.data.attributes.tagsโ echoes the applied tag.meta.client_actions[0]โ the upload descriptor +pollblock.
The tag literal is also mirrored into {{fac_tag}} for step 05.
โถNext Step
โ Step 2: Wait For Facility Staged.