not_implemented

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: 501

​

Message

This endpoint or request shape isn’t implemented yet — see the message for the workaround and the v1.1 timeline. Don’t retry; the response won’t change until the feature ships.

​

When you’ll see this

Today, the only path that returns not_implemented is:

• PATCH /v1/devices/{device_id} with an assignment object in the body.

The read side of assignments is fully available:

• active_assignment is embedded on GET /v1/devices and GET /v1/devices/{device_id}
• Assignment history at GET /v1/devices/{device_id}/assignments
• Time-scoped readings at ?assignment_id= on both /readings and /readings.csv

What’s reserved for v1.1 is the write side: opening, transferring, or closing an assignment via the public API.

​

Fix

Two options today:

1. Use the dashboard. Go to dashboard.1st.app, open the device, and assign, transfer, or unassign from the UI. The same dashboard action that a coach would take from the device detail page.
2. Use the read endpoints only. If your integration just needs to know what each device is currently tracking, the active_assignment embed on GET /v1/devices covers that without ever mutating.

​

Don’t retry

not_implemented is a permanent answer for the current API version. A retry loop that branches on 5xx status will hit it forever. Branch on code instead — not_implemented is a stable string. We’ll add a separate code (and a 200 response) when the v1.1 write surface ships.