Manually ingest a meeting

Manually ingest a meeting with meeting metadata, recording file and transcript file. The metadata includes meeting title, provider name, participant details, meeting & recording time

Note:

Recording file size limit is up to 2GB and required file extension is .mp4. The transcript file extension should be .json.

REQUEST INPUTS

1. MetaData: The metadata contains meeting details as given below.
Meeting metadata is required in request input.

FieldTypeRequiredDescription
TitlestringYesMeeting title
ProviderstringYesName of meeting provider (Zoom, Webex, Microsoft Teams)
MeetingStartDateTimestringYesMeeting start date time in UTC format
MeetingEndDateTimestringYesMeeting end date time in UTC format
RecordingStartDateTimestringNoMeeting recording start date time in UTC format
RecordingEndDateTimestringNoMeeting recording end date time in UTC format
ParticipantsJSON object arrayYesList of meeting participants
Participant detailJSON objectYesMeeting participant details

Participant detail object fields:

FieldTypeRequiredDescription
NamestringYesName of meeting participant
EmailstringNoEmail of meeting participant (Not mandatory for participant type 'Participant')
EmailstringYesEmail of meeting participant (Mandatory for participant type 'Host')
PhoneNumberstringNoParticipant phone number
TypestringYesParticipant type Host or Participant

Sample Metadata:

Sample Metadata:

{
	"Title": "Daily Sync Call",
	"Provider": "Zoom",
	"MeetingStartDateTime": "2025-01-28T01:32:35Z",
	"MeetingEndDateTime": "2025-01-28T01:40:35Z",
	"Participants": [
		{
			"Name": "Ram D",
			"Email": "[email protected]",
			"PhoneNumber": "123-456-7890",
			"Type": "Host"
		},
		{
			"Name": "Jane Smith",
			"Email": "[email protected]",
			"PhoneNumber": "098-765-4321",
			"Type": "Participant"
		}
	]
}

2. RecordingFile: Meeting recording file with .mp4 extension. Recording file is optional to manually ingest meeting.

3. TranscriptFile: Meeting transcript file with .json extension. Transcript file is optional to manually ingest meeting.

Validation rules & errors

Manually Ingest meeting API validates incoming request. The table below provides validation rules, error codes, and corresponding error messages. If there are multiple errors in the request, only the first one captured is returned.

Validation RuleError CodeError Message
Meeting provider is invalid400Meeting provider should be one of the following (Zoom,Webex,Teams).
Meeting RecordingStartDateTime date is greater than current date & time400Recording start date time must be less than current date time.
Meeting RecordingEndDateTime date is greater than current date & time400Recording end date time must be less than current date time.
No participant with participant type 'Host'400At least one participant should be Host with a valid email registered with Seismic.
No recording/transcript file provided400Upload at least one recording or transcript file for the meeting.
Multiple recording files provided400At most only one recording file can be uploaded.
Multiple transcript files provided400At most only one transcript file can be uploaded.
Language
Credentials
Header
Click Try It! to start a request and see the response here!