Users
Available since: v1.0.0
| File | Snapshot | Delta | Frequency |
|---|---|---|---|
| users/users_yyyy_MM_dd.csv | :white_check_mark: | :white_check_mark: | Daily |
[block:parameters] { “data”: { “h-0”: “Attribute”, “h-1”: “Required?”, “h-2”: “Value”, “h-3”: “Description”, “0-0”: “USER_ID”, “0-1”: “Yes”, “0-2”: “NUMBER”, “0-3”: “Id field used to uniquely identify user.”, “1-0”: “LOGIN”, “1-1”: “Yes”, “1-2”: “VARCHAR2(64 BYTE)”, “1-3”: “Username used for login”, “2-0”: “FIRST_NAME”, “2-1”: "", “2-2”: “VARCHAR2(40 BYTE)”, “2-3”: "", “3-0”: “MIDDLE_NAME”, “3-1”: "", “3-2”: “VARCHAR2(40 BYTE)”, “3-3”: "", “4-0”: “LAST_NAME”, “4-1”: "", “4-2”: “VARCHAR2(40 BYTE)”, “4-3”: "", “5-0”: “EMAIL”, “5-1”: “Yes”, “5-2”: “VARCHAR2(64 BYTE)”, “5-3”: "", “6-0”: “EMAIL_STATUS”, “6-1”: "", “6-2”: “NUMBER”, “6-3”: “1 = verified \n2 = not verified”, “7-0”: “RECEIVE_EMAIL”, “7-1”: "", “7-2”: “0 or 1”, “7-3”: “The front-ends can pass this along to indicate that the user has agreed to receive newsletters or other non subscription-related information from the service”, “8-0”: “GENDER”, “8-1”: "", “8-2”: “NUMBER”, “8-3”: “Determined by front-end how it’s set (e.g. 1=Male, 2=Female)”, “9-0”: “DATE_OF_BIRTH”, “9-1”: "", “9-2”: “DATE”, “9-3”: "", “10-0”: “PHONENUM”, “10-1”: "", “10-2”: “VARCHAR2(15 BYTE)”, “10-3”: "", “11-0”: “MOBILENUM”, “11-1”: "", “11-2”: “VARCHAR2(15 BYTE)”, “11-3”: "", “12-0”: “MOBILE_STATUS”, “12-1”: "", “12-2”: “0 or 1”, “12-3”: “Can be used to indicate that mobile number has been verified”, “13-0”: “RECEIVE_SMS”, “13-1”: "", “13-2”: “0 or 1”, “13-3”: “Can be set to indicate that the end-user has agreed to receive sms from the service”, “14-0”: “ADDRESS”, “14-1”: "", “14-2”: “VARCHAR2(64 BYTE)”, “14-3”: "", “15-0”: “POSTAL_CODE”, “15-1”: "", “15-2”: “VARCHAR2(10 BYTE)”, “15-3”: "", “16-0”: “CITY”, “16-1”: "", “16-2”: “VARCHAR2(30 BYTE)”, “16-3”: "", “17-0”: “STATE”, “17-1”: "", “17-2”: “VARCHAR2(20 BYTE)”, “17-3”: “As in “Texas”, “Califorinia"", “18-0”: “COUNTRY”, “18-1”: "", “18-2”: “VARCHAR2(40 BYTE)”, “18-3”: "", “19-0”: “STATUS”, “19-1”: "", “19-2”: “NUMBER”, “19-3”: “Used to delete users that have been inactive for a long period. This is not done automatically, but upon request. \n0 or null = active \n1 = passive \n2 = delete_warning sent to user \n3 = deleted (by system) \n4 = deleted (by admin) \n5 = frozen ( For customers who have voluntarily suspended their account ) \n6 = blocked ( For customers who haven’t paid their bills )”, “20-0”: “STATUS_DATE”, “20-1”: "", “20-2”: “DATE”, “20-3”: “Date the status was updated”, “21-0”: “NICKNAME”, “21-1”: "", “21-2”: “VARCHAR2(40 BYTE)”, “21-3”: "", “22-0”: “INFO_RESTRICTED”, “22-1”: "", “22-2”: “0 or 1”, “22-3”: "", “23-0”: “CURRENT_PLAYQUEUE_ID”, “23-1”: "", “23-2”: “NUMBER”, “23-3”: “Used to keep track of the main play queue of the user”, “24-0”: “RECEIVE_FAVORITE_EMAIL”, “24-1”: "", “24-2”: “0 or 1”, “24-3”: “Indicates if the user wants to receive e-mails with update on shows marked as favorite”, “25-0”: “UPDATE_TIME”, “25-1”: "", “25-2”: “DATE”, “25-3”: "", “26-0”: “REIGSTRATON_DATE”, “26-1”: "", “26-2”: “DATE”, “26-3”: "", “27-0”: “JWT_SUBJECT_ID”, “27-1”: "", “27-2”: “VARCHAR2(256 BYTE)”, “27-3”: “If user is migrated, this column holds the ID of the user in the identity provider. The format of the value is {issuer}|{subject} as seen in the token issued by the identity provider. \nAvailable since 2.9.0” }, “cols”: 4, “rows”: 28, “align”: [ “left”, “left”, “left”, “left” ] } [/block]