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

FieldRequiredNotes
location_typeYesfacility for this workflow
commodity_typeYese.g. coffee
tagsYes (here)One or more free-form strings (โ‰ค100 chars). The workflow's selection key โ€” used by step 05's filter.tag.
metricsNoOmit 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 + poll block.

The tag literal is also mirrored into {{fac_tag}} for step 05.

Next Step

โ†’ Step 2: Wait For Facility Staged.