Add a possession type
Add a kind of thing your account owns. Add its groups and fields afterwards.
The change is written to the account log.
Body parameters
Sent as JSON. Anything not listed here is ignored.
What the kind of thing is called. Up to 255 characters. Markup and surrounding blank space are stripped, and a name left with nothing in it is refused.
One of the vault colours: #3f5fd0, #4f8a49, #9a6a24, #9a3f2b, #6b4fa8, #2f7f86, #a8447a or #4a4a52. Blue when left out.
One of the glyphs of the catalogue. Anything else answers 422. None when left out.
Returns
The possession type object that was added, with no group and no field yet.
The possession type.
Always possession_type. 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 kind of thing is called.
One of the eight vault colours, as a hexadecimal value.
One of the glyphs of the catalogue (the same list sections and possession conditions use), or null. A type without one is drawn with a blank page.
How many fields the type has, which is 0 for a new one.
The groups of fields, an empty list for a new type.
The standalone fields, an empty list for a new type.
When the type was added, as a count of seconds since 1970.
When it last changed, as a count of seconds.
Where to find this record.
The absolute address this record is read from.
The screen where the possession type is edited 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.