Skip to main content

Data Types

Our data types are generally well aligned with JSON data types.

For data integration, you should consider following data types:

String​

  • For storing alphanumeric data
  • Most of our fields primarily accept ASCII character set
  • Only certain fields accept Unicode - primarily the name and address fields

Number​

There can be two type of number fields:

  • Integers
  • decimals

Boolean​

true/ false

Date/ Time​

JSON doesn't has built in Date/ Time data type. Hence, we generally encode dates in ISO date formats unless indicated.

Some additional considerations:

Timezone​

Almost all of the event data generated by our system represents the data in UTC. Most of our APIs also return the data both in UTC and Local Time Zone format. When working across multiple timezones, converting from UTC to local or identifying the timezone for local time may be confusing.

Our general rule of thumb is:

  • Local Time represents the time of the location of the unit when the data was captured
  • Modification timestamp data only stores data in UTC

JSON​

It is not a data type in itself. However, some data elements may return string encoded JSON to represent complex data. For example, an image can have product analysis with multiple attributes. So, you get a sting similar to the following:

{
  "tags": [
    {
      "ProductId": 24665,
      "HasTag": 0,
      "StockLevelList": [],
      "StockLevel": 0,
      "TierList": [
        2
      ],
      "Tier": 2,
      "isEmpty": false,
      "IsForeign": false
    },
    {
      "ProductId": 24664,
      "HasTag": 0,
      "StockLevelList": [],
      "StockLevel": 0,
      "TierList": [
        2
      ],
      "Tier": 2,
      "isEmpty": false,
      "IsForeign": false
    }
  ]
}```