List possession conditions
List every possession condition of your account, in the order the account keeps them.
A possession condition belongs to the account, not to a vault. Every account starts with six: New, Like new, Used, Worn, Damaged and Broken, in the language of the person who created it.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Query parameters
Sent as JSON. Anything not listed here is ignored.
Which page to answer with.
How many conditions one page holds, between 1 and 100. A number outside the range is brought back into it.
Returns
A page of possession condition objects, and how many there are in all. An account with none answers an empty list.
The possession conditions on this page. An empty list rather than an error when there are none.
One 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.
Where you are in the collection.
The page this is, counting from 1.
How many one page holds, which is the size that was asked for once it has been brought into the allowed range.
How many possession conditions there are in all, not how many are on this page.
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.