Information in a member's Personal Data Store (PDS) is stored as series of datasets. A dataset might, for example, represent information pertaining to the member's driver's license, passport or house. A member can also have multiple instances of a dataset. For instance, a member may have a second instance of the 'Home' dataset containing details of a second address.
Each member has control over how organisations access their datasets by changing the access permissions on the connection between their PDS and the organisation.
||Details of a member's bank account||Production|
||Details of a member's community profile.||Production|
||Details of the member's credit cards.||Production|
||Data relating to a members driving licence||Production|
||Data relating to a members education history||Production|
||Details of each employer.||Production|
||High-level health and GP details.||Production|
||Data relating to a members home||Production|
||Data relating to a members Local Authority||Production|
||Data relating to a member's loyalty schemes.||Production|
||Data relating to a members National Insurance details||Production|
||Notes made by a member.||Production|
||Data relating to a members passport details||Production|
||Data relating to a members personal details||Production|
|Place of Birth||
||Data relating to a members date & place of birth||Production|
||Details of travel arrangements.||Production|
||Television licence details.||Production|
|Utility Account Details||
||Data relating to a members utilities accounts||Production|
||Details of vehicles owned.||Production|
||Details of voluntary activities.||Production|
While some datasets change infrequently like the ones listed above, other datasets are updated constantly. Examples include browser history, bank transactions, and the call records in your mobile bill.
These are referred to as Transactional Datasets. The distinctions between an API call made to a regular Dataset and a Transactional Dataset are given in the Connection API table.
||Logs all assurance records.||Production|
|Bank Account Transactions||
||Bank account transactions||Production|
||User browsing history||Production|
||Details of the member's credentials (passwords) and associated details.||Production|
|Credit Card Transactions||
||Credit card transactions||Production|
|Device App Settings||
||Table for storing device app setting variables.||Production|
||Records of devices.||Production|
|Identity Protocol Settings||
||Stores Identity protocol settings.||Production|
||Identity Services Log||Production|
||Location data from devices.||Production|
||Loyalty scheme data||Production|
|Telephone Calls and SMS||
|Utility Billing Records||
|Utility Data Usage||
|Utility Meter Reading||
||Utility meter readings||Production|
||Table for storing variables.||Production|
The Developer Namespace Dataset
The Developer Namespace Dataset enables developers to 'simulate' storing data against a dataset that is not yet available by allowing developers to save custom serialised JSON data to a connection. Any data can be stored inside this namespace, as long as it is valid JSON. This feature could be used to store Application or Connection state data; data that is not currently supported in the Master Schema.
Each developer’s namespace data is stored separately from each other, based on the developer’s API key. This means that a developer cannot access another developer’s namespace data. This feature is only available in the Sandbox environment.
New datasets to cover new use-cases are constantly being added to the platform. These start out on the Sandbox environment at https://sbx-api.mydex.org before graduating to the live platform at https://api.mydex.org.
If there's a dataset you want to see added, please let us know by filling out our dataset request form.