Accounts

Multiple Operators can be associated with an EVRYTHNG Platform account. Through use of the Roles API each can be given the appropriate permissions and levels of scope necessary for their role in the application.

From each Operator's perspective, they each have a unique access to each account they are associated with, and are granted an Operator API Key for each.

API Status General Availability: /accounts /accounts/:accountId /accounts/:accountId/shortDomains /accounts/:accountId/domains

AccountDocument Data Model

❗Account Configuration API

See the Account Configuration section for full details on the account configuration functionality.

Filterable Fields

This resource type can be filtered using the following fields and operators.

AccessDocument Data Model

The AccessDocument contains role and authentication information for an account.

Read All Accounts

Read an array of all accounts visible to an Operator with their API key.

Read an Account

Read an account by its ID by sending a GET request to the /accounts/:accountId endpoint.

Update an Account

Update an account with new user information or custom fields by sending an AccountDocument with only the fields to be updated. For example, the name, or imageUrl which will be displayed in the Dashboard.

Update Account Configuration

❗Deprecation

There's a new way of handling account configurations!\nCheck out the new Account configurations API.\n\nManaging account configurations via accounts/:accountID will be deprecated on September 30th 2021.

Unique identifiers

Follow the syntax below for updating unique identifier account configuration.

Products

A single unique identifier per Product is supported.

Configuration is an array of identifier keys in configuration.uniqueIdentifiers.products. For example, if your array consists of ["gs1:01", "gs1:22", "gs1:8003"], then any product that has one or more of those identifier keys will have a unique identifier value associated with it.

The unique identifier is additive in array order, so if the product has multiple qualifying identifier keys then the unique identifier for the product will be a pipe-delimited concatenation of these values, e.g. gs1:01:1234|gs1:22:5678.

Attempting to create or update another Product with the same unique identifier will result in a 409 conflict error response.

Thngs

Multiple unique identifiers per Thng are supported.

Configuration is an array of objects in configuration.uniqueIdentifiers.thngs. Each object represents a potential matching unique identifier on a Thng, so the maximum possible number of unique identifiers for a given Thng is equal to the number of objects in the array.

Thng identifier uniqueness supports concatenation of the Thng's Product identifier and one or more Thng identifiers.

For example, consider the following configuration:

If a Thng has the following identifiers: gs1:21:10230456, gs1:250:AxBCxDEF

And its associated Product has the following identifier: gs1:01:90870654

Then two unique identifier values will be created: gs1:01:90870654|gs1:21:10230456, gs1:250:AxBCxDEF

Attempting to create or update another Thng with the same gs1:250 value, or the same combination of gs1:01 (on the Product) and gs1:21 (on the Thng) values will result in a 409 conflict error response

The combination of a gs1:01 identifier key on a Product and a gs1:21 identifier key on a Thng is also known as a Serialized GTIN, or SGTIN. This data can also be embedded in an RFID tag as an Electronic Product Code, or EPC.

Read Account Accesses

Read all available accesses to an account. This translates to the list of Operators who are listed as team members.

Read an Account Access

Read a single account access by ID.

Read all Short Domains

Read all short domains available to an account.

DomainDocument Data Model

Read all Domains