Move a possession condition
Move a possession condition to another place in the order. The others shift to make room.
A position past the end puts the condition last. The change is written to the account log.
Parameters
Sent as JSON. Anything not listed here is ignored.
The id of the possession condition. A condition belonging to somebody else answers 404.
Where it goes, counting from 1.
Returns
The possession condition object at its new place.
The possession condition.
Always possession_condition. 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 the condition reads, such as New or Broken.
One of the eight vault colours, as a hexadecimal value.
One of the glyphs of the catalogue, or null when the condition has none.
Its place in the order the account keeps, from best to worst, counting from 1.
When the condition 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 settings screen where the conditions of the account are managed, 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.