Data source reference

BETA documentation generated on: December 06th 2018

Data format

When a user consents to your app accessing their data, the digi.me API will asynchronously prepare that data for download. The data will be made available in a series of files and each filename will describe the kind of data that is available in it.

The filenames follow this naming convention:

{Version}_{ServiceGroup}_{Service}_{AccountId}_{ObjectType}_{DateRange}_{Flag}.json

A file list response might look like this:

[
	18_1_1_1_1_D201504_1.json,
	18_2_16_10_136_D201005_1.json,
	18_3_17_50_201_D201810_1.json,
	18_5_19_6_406_D201712_1.json,
	...
]

Using the above convention, the file name `18_1_1_1_1_D201504_1.json` would resolve to:

{Version:18}_{ServiceGroup:1}_{Service:1}_{AccountId:1}_{ObjectType:1}_{DateRange:201504}_{Flag:1}.json

i.e,

Item
Resolved Value
Version
18
Service Group
Social
Service
Facebook
(digi.me Library) AccountId
1
Object Type
Posts
Date (from YYYYMM)
April 2015
(Internal) Flag
1

Service Groups

High level service groups

Group ID
Group Type

Services

Available services that we currently support

Service ID
Service Type
Service Group
1
Facebook
3
Twitter
4
Instagram
9
Pinterest
12
Flickr
17
Finance
19
Spotify
20
OpenEpic
31
YouTube

Objects

Available objects that we currently support

Object ID
Object Type
Service Group
100
Admission (IS. Health)
101
ArrivalAmbulatory (IS. Health)
102
ArrivalPrimaryHealth (IS. Health)
103
Prescription (IS. Health)
104
Medication (IS. Health)
105
Diagnosis
105
Diagnosis (IS. Health)
106
Vaccination
106
Vaccination (IS. Health)
107
Allergy
107
Allergy (IS. Health)
108
ArrivalEmergency (IS. Health)
109
PrescribedItem (IS. Health)
111
Measurement (IS. Health)