/api/v1/todos/{todo}
Get a to-do
Read one to-do from any record type the token can manage to-dos for.
Last updated
Request
GET /api/v1/todos/{todo}
Requires at least one of assets:todos, people:todos, locations:todos, or subscriptions:todos. See token permissions.
Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json.
todo is the numeric to-do ID.
Query parameters
This endpoint does not use query parameters.
Example
Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example record and option IDs with values from your organization.
curl --request GET "https://my.assetcenter.app/api/v1/todos/77" \
--header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
--header "Accept: application/json"
Response
200 OK.
{
"data": {
"id": 77,
"name": "Replace battery",
"notes": null,
"due_date": "2026-10-09",
"assigned_to": 4,
"created_by": 4,
"is_complete": false,
"created_at": "2026-10-02T16:00:00.000000Z",
"updated_at": "2026-10-02T16:00:00.000000Z",
"resource": "assets",
"record_id": 123
}
}
Behavior and constraints
A token sees only to-dos on record types it holds the :todos permission for; for example, a token with only assets:todos never sees to-dos on people. resource and record_id identify the record the to-do belongs to. assigned_to and created_by are organization user IDs, not people. A to-do on a record type the token lacks :todos for, or in another organization, returns 404. To read its comments and files, use the record’s timeline entry with type todo.
Errors
401 means the token is missing, expired, revoked, or not a customer API token. 403 means a required permission or administrator access is missing. 404 means the to-do is unavailable to this token. 422 identifies invalid or unsupported input; inspect the errors object when present. 429 means a rate limit was reached. See error handling and rate limits.