Add a possession tag
Add a word your account can put on its possessions.
The change is written to the account log.
Body parameters
Sent as JSON. Anything not listed here is ignored.
What the tag reads. Up to 50 characters. Markup and surrounding blank space are stripped, and a name left with nothing in it is refused. A name another tag of the account already has, ignoring case, is refused with “You already have a tag with this name.”
One of the vault colours: #3f5fd0, #4f8a49, #9a6a24, #9a3f2b, #6b4fa8, #2f7f86, #a8447a or #4a4a52. Blue when left out.
Returns
The possession tag object that was added.
The possession tag.
Always possession_tag. 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 tag reads, such as Insured or To sell.
One of the eight vault colours, as a hexadecimal value.
When the tag was added, as a count of seconds since 1970.
When its name or colour 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 tags 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.