Get a transaction
Retrieve one transaction of a possession.
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.
The id of the transaction. A transaction of another possession answers 404.
Returns
A transaction object. A vault, a possession or a transaction of another account answers 404.
The possession transaction.
Always possession_transaction. 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 happened: purchase, sale, exchange, gift_received, gift_given, inheritance, refund, fee, tax, shipping or other.
Whether the possession changed hands, true for the first six types and false for the money only ones.
Whether this is the transaction that brought the possession in: its earliest purchase, exchange, gift received or inheritance, undated ones first.
The day it happened, written as 2005-03-14, or null when it is not known.
Who was on the other side, as text, or null.
The price or the amount, as a string with two decimals, or null.
The tax paid, or null.
The fees paid, or null.
The shipping paid, or null.
The total typed in, which overrides the sum of the four figures, or null.
The total of the transaction: the entered total, else the sum of the figures set, else null.
Where the total comes from: entered, sum or unknown.
The currency of every figure, in lower case, or null when no figure is set. Nothing is ever converted.
An invoice, receipt or deed number, or null.
Where the transaction can be checked, or null.
Anything worth remembering about it, or null.
The invoices, receipts and deeds attached to it, oldest first.
One document.
The id of the file, which is what removing the document takes.
The name of the file as it was uploaded.
The kind of the file, such as application/pdf.
How much storage the file takes.
When the transaction was recorded, 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 Transactions 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.