List the timeline of a possession
List everything that happened to a possession, the newest first.
An entry comes from each transaction, insurance record, valuation, provenance event, maintenance record and stay, and from each loan once it started and again once it came back. A planned loan gives none. A provenance event that a loan or a transaction wrote gives none, since the loan or the transaction already gives that moment.
On the same day, the latest recorded comes first. Entries without a date come last.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
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.
Only the entries of this section: transactions, insurance, valuations, provenance, maintenance, loans or locations. Anything else answers 422.
Returns
Every entry of the timeline, or an empty list. A vault or a possession of another account answers 404.
Every entry of the timeline, whole rather than a page at a time, the newest first and the undated last.
One entry.
Always possession_timeline_entry. An entry is computed, so it has no id of its own.
What the entry says.
The section it is read from: transactions, insurance, valuations, provenance, maintenance, loans or locations.
What happened: transaction, insurance, valuation, provenance, maintenance, loan_started, loan_returned or stay. A loan that came back gives two entries, one of each loan kind.
When it happened, written as 2026-11-02, or null when nobody knows.
How precise the date is: day, month, year, circa or unknown. Only a provenance event is ever less precise than a day.
Whether this is the valuation giving the current value, or the stay where the possession is now.
Whether this transaction brought the possession in: a purchase, an exchange, a gift received or an inheritance.
The id of the record the entry is read from.
Where to find the record.
The absolute address the record is read from, in its own section.
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.