The following table outlines the possible fields which can be expected in the API response.
|id||string||Validic user ID|
|uid||string||Customer’s user identifier.|
|marketplace > token||Unique marketplace identifier.|
|marketplace > url||string||The user’s marketplace URL. Requesting this URL with the ‘Accept’ header as ‘application/json’ will provide a JSON representation of the marketplace. Otherwise an HTML representation will be presented.|
|mobile > token||string||Unique identifier used to connect users to the Validic mobile solution.|
|location > timezone||string||Default user timezone. When retrieving data from a source that provides no UTC offset information the default timezone will be used to calculate the UTC offset.|
|location > country_code||string||User’s country identified as a two character country code using the ISO 3166-1 standard. Validic uses this information for integrations that provide data access based upon the user’s country.|
|sources||string||List of sources the user has connected to including the connection time in UTC.|
|created_at||string||The date and time the resource was created.|
|updated_at||string||The date and time the resource was updated.|
|last_processed_at||string||The date and time data was last processed for this source.|
Validic supports over 400 Olson format timezones. When setting a default timezone for a user the value must match one of the timezones listed in the table found in our support section.