List the maintenance records of a possession
List every maintenance record of a possession, the latest job first.
The record with the latest day performed comes first, and on the same day the one added last comes first. The first record is therefore the only one that can be overdue. The list is whole rather than paginated.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Path parameters
Sent as JSON. Anything not listed here is ignored.
The vault the possession is kept in, named either by the readable name it reports as slug or by its id. A vault of another account answers 404.
The id of the possession. A possession of another vault or of another account answers 404.
Returns
Every maintenance record object of the possession, or an empty list. A vault or a possession of another account answers 404.
Every one of the possession maintenance records, whole rather than a page at a time.
One possession maintenance record.
Always possession_maintenance_record. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
What kind of job it was: inspection, cleaning, servicing, repair, restoration, part_replacement, conservation or other.
What was done, as text.
The person or the workshop who did the job, as text, or null.
The day the job was done, written as 2026-03-12.
What the job cost, as a string with two decimals, or null when it is not recorded. It is never added to the transactions or to the declared value of the possession.
The currency of the cost, in lower case, or null when there is no cost. Nothing is ever converted.
The possession condition the possession was in before the job, or null when it is not recorded. A condition renamed since gives its new name, and one deleted since leaves null.
The id of the condition, as the possession conditions endpoints give it.
What the condition is called.
The possession condition the possession was in after the job, or null when it is not recorded. A condition renamed since gives its new name, and one deleted since leaves null.
The id of the condition, as the possession conditions endpoints give it.
What the condition is called.
The day the job should be done again, or null when nothing is scheduled.
Whether the job is due again and has not been done. Only the latest record of the possession can be overdue, since a later job replaces the schedule of an earlier one, and it is overdue when its next due date is before today, in the timezone of the user the key belongs to. It is read, never written.
What was found and what was done, or null.
When the record was added, as a count of seconds since 1970.
When it last changed, as a count of seconds, or null.
Where to find this record.
The absolute address this record is read from.
The Maintenance section of the possession in the application, which opens for somebody signed in rather than for a key. It is the link to give a person.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.