Skip to main content

Documentation Index

Fetch the complete documentation index at: https://dev.1st.app/llms.txt

Use this file to discover all available pages before exploring further.

HTTP status: 404

​
Message

No assignment with this ID exists on this device, or the ID isn’t visible to your team. List assignments via GET /v1/devices//assignments to get valid IDs for the right device.

​
Common cause

  • You pasted the wrong assignment_id. Each ID belongs to one specific device. Using an ID from device A while asking about device B returns this error.
  • The assignment ID belongs to a device on a different team than the one your API key is for.
  • You used a placeholder UUID like 00000000-0000-0000-0000-000000000000.
We deliberately don’t tell you whether the ID exists somewhere else on your team. That keeps the response from being a way to discover other devices’ assignment IDs by guessing.

​
Fix

Get the right assignment_id from the device’s history first: 
curl -H "Authorization: Bearer $ST_API_KEY" \
  "https://api.1st.app/v1/devices/{device_id}/assignments"
Each row’s assignment_id is valid for that specific device. Use it in:
  • GET /v1/devices/{device_id}/readings?assignment_id=<id> to scope readings to one period
  • GET /v1/readings.csv?assignment_id=<id> for the same scoping on the bulk CSV export
The currently-open assignment also appears as active_assignment.assignment_id on GET /v1/devices/{device_id}, so you don’t always have to list history.