phone_number
or postal_address
.API_SUBSCRIPTION_KEY
by signing up for the API, then use the CLI tool to generate a User and access token.)item_templates
key. Each Template object has a slot_ids
list, which references Slots in the top-level slots
list.passport_details
password
important_document
vehicle
travel
bank_item
membership_subscription
pet
device
important_document
custom
services
id
(replace ITEM-TEMPLATE-ID
):label
text (replace SEARCH_TEXT
):vehicle
Template.vehicle
Template has the following Slots:model_make
licence_plate
vin
type
purchase_date
name
is auto-generated from its label. Names are all lower-case, have no non-alphanumeric characters, and have whitespace replaced with underscores. For example, label A strange &8Label
would become a_strange_8label
.slots_attributes
are created for the new Item.my_template
had Slots foo
and bar
, and we create an Item withfoo
, bar
and baz
.label
property is required, it will auto-generate a name
(as described above). Since Item Templates are referenced by their name, the generated name must be unique. You can specify it separately if the label does not generate a unique name.description
property inherits the description
of the Item Template.encrypted_value
data that doesn't match the cryppo serialization format.name
label
description
encrypted_value
slot_type_name
slot_type_name
property must be one ofkey_value
bool
classification_node
color
date
datetime
image
note_text
select
attachment
url
phone_number
select_multiple
email
password
key_value
is the default.slots_attributes
property when creating an Item. Since they are keyed by name
, either label
or name
must be non-empty on creation.PUT /vault/items
with the new data in slots_attributes
:DELETE /slot/id
. This deletes the Slot (and it's data) from the parent Item..item_config.yaml
using the current user's keys.UserService
.PUT https://sandbox.meeco.me/vault/incoming_shares/{share_id}/accept
. (This indicates you accept the share terms, if any). Next call GET https://sandbox.meeco.me/vault/incoming_shares/{share_id}/item
and view the Item that has been created in your Vault. Note that share.item_id
is the original Item's id, not the one in your Vault!own
original_id
share.item_id
share_id
share.id
item.share_id
is non-null, then it is a share you received, and you can view the share via GET https://sandbox.meeco.me/vault/incoming_shares/{item.share_id}
.item.sharing_mode
is anyone
.