Data source reference

BETA documentation generated on: December 2nd 2019

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

Services

Available services that we currently support

Service ID
Service
Service Group
1
Facebook
3
Twitter
4
Instagram
9
Pinterest
12
Flickr
16
Iceland Health
17
Finance
18
Fitbit
19
Spotify
20
Epic BETA
21
Garmin
25
DVLA
30
EMIS BETA
31
YouTube
32
Plaid
33
Google Fit BETA

Objects

Available objects that we currently support