Archive chat file format

What is the format of archived chat file for meetings fetched using Archive api?
Is the file format published somewhere?
A sample message obtained from the archive api is pasted below:
00:01:02 Vivek J(16778240, Ok, here are some chats for this archived meeting

It will be helpful to know more about the file format as we write a parser.

Which App Type (OAuth / Chatbot / JWT / Webhook)?

Which Endpoint/s?
/archive_files (described here)

Additional context
We need to write a parser that will parse the chat text file for our compliance platform. It will be helpful to know the file format.

Hi @vivek.thetalake ,

Here’s the file types that can be returned via that endpoint:

The chat file is in the form of a TXT file.


Thanks for replying. We know both of those things.
The question is about the details of the format of the text file in which chats are returned, including all use cases, so our parser is reliable and does not break for use cases we did not know based on simple test data.

Let me give an example. The following is a line from a chat file:
00:01:02 Vivek J(16778240, Ok, here are some chats for this archived meeting

This line from the chat file can be deconstructed as:

  • the first field seems to be the local time when the message was posted, followed by a tab (\t)


  • Then the first name and last name of the participant who posted (with one space between them)

Vivek J

  • Followed by 2 comma separated data points in parentheses: 1) some number, which is not the account number, and 2) email id of the participant, followed by colon character and tab (\t): `


  • And the message in the end

Ok, here are some chats for this archived meeting

Sorry if format is not the correct word, perhaps the right word for what we are looking for may be schema or layout of fields in the text file and the separators or terminators used. This will help in tokenizing and parsing all types of data that can come in the chat file.

Hi @vivek.thetalake ,

Thanks for the additional context! The documentation you’re seeking does not exist at the moment, but you can submit a #feature-requests for this.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.