Data export

Admins of organizations can export all of their team's data on Threads, including all private chats and channels. The data export can be initiated from Organization Settings:

Note: if you are not an admin, you can export individual Threads as PDFs. See details here.

The export is structured in a .JSON format. Below is a the structure of the data export .zip file:

• channels/

  • <threadID/>

    • thread.json

    • <fileID_fileName.extension>

• channels.json

• chats/

  • <chatID/>

    • <timestamp_1>.json

    • <timestamp_2>.json

    • <fileID_fileName.extension>

• chats.json

• private/

  • <userID/>

    • thread.json

    • <fileID_fileName.extension>

• users.json

users.json - a list of users who was an audience member of a thread or chat included in this export id: Threads userID firstName: Threads user's first name lastName: Threads user's last name primary Email: the primary email associated with the thread's users account

channels.json - metadata for channels for threads are included in this export name: channel name description: channel description text creatorID: the Threads userID who created the channel memberIDs: a list of threads userIDs who were members of the channel at the time of export privacy: whether the forum is public or private createdTimestamp: unix timestamp in milliseconds of when the channel was created

channels/ - Each thread associated with this channel is allocated a distinct folder. Inside the folder named after the thread ID (<threadID/>), you will find a file named thread.json, which stores content pertaining to the thread. Additionally, attachments included within the thread are saved as separate files within the same <threadID/> folder.

private/ - Each private user thread that does not belong to any channel is allocated a distinct folder of the user who created it. Inside the folder named after the userID (<userID/>), you will find a file named thread.json, which stores contents pertaining to the thread. Additionally, attachments included within the thread are saved as separate files within the same <threadID/> folder.

thread.json - thread contents

threadID: unique identifier of the thread contentType: type of content authorID: unique identifier of the author of the authorName: first and last name of the author blocks: list of blocks that contain the contents of the block in plaintext and markdown createdAt: timestamp when the content was created title: title of the thread comments: list of blocks that are replies to the thread audienceIDs: list of Threads userIDs who have access to the thread

chats.json - metadata for chats included in this export

chatID: chat unique identifier name: chat name creatorID: the Threads userID who created the chat memberIDs: a list of Threads userIDs who were members of the chat at the time of export createdTimestamp: timestamp when the chat was created

chats/ - Each chat is represented by its own folder, labeled with the chat's ID (<chatID/>). Inside this folder, chat messages are stored in files named by timestamp (<timestamp>.json). Each of these files contains up to 50,000 chat messages. Additionally, files corresponding to any attachments sent within the chat are also stored within the <chatID/> folder, each named after the attachment

<timestamp.json> - chat message contents (up to 50,000 chat messages per file):

messageID: message unique identifier chatID: chat unique identifier actorID: unique identifier of the author of the message timestamp: 'when timestamp at which the message was created plainText: text of the message with no formatting markdown: the message in markdown format