GuidesAPI DocsChangelogMy AppsSeismic Exchange
API Docs

Manually ingest a meeting

post
https://api.seismic.com/meetings/v1/meetings/manuallyIngest

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

Note:

Recording file size limit is up to 2GB. Supported recording file extensions: .mp4, .mp3.
The transcript file extension must be .json for all providers except Manual Upload.
For the Manual Upload provider, transcript files may use .json, .vtt, .xml, or .txt.

REQUEST INPUTS

1. MetaData: Meeting details serialized as a JSON string. Meeting metadata is required in the request.

FieldTypeRequiredDescription
TitlestringYesMeeting title
ProviderstringYesName of the meeting provider. Must be one of: Zoom, Webex, Microsoft Teams, Google Meet, Zoom Phone, Gong, Manual Upload
MeetingStartDateTimestringYesMeeting start date and time in ISO 8601 UTC format
MeetingEndDateTimestringYesMeeting end date and time in ISO 8601 UTC format
ParticipantsJSON object arrayYesList of meeting participants

Participant object fields:

FieldTypeRequiredDescription
NamestringYesFull name of the participant
EmailstringYes (Host) / No (Participant)Email address. Required for participants of type Host and must belong to a valid Seismic user
PhoneNumberstringNoParticipant phone number
TypestringYesParticipant role: Host or Participant. If multiple participants are marked as Host, the first one with a valid email is used

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 (.mp4 or .mp3). Recording file is optional.

3. TranscriptFile: Meeting transcript file. Transcript file is optional.
For all providers except Manual Upload, the file must be .json and each entry must conform to the following schema:

[
  {
    "Id": 1,
    "Start": 0,
    "Speaker": "Ram D",
    "End": 15000,
    "Text": "Hello, welcome to the meeting."
  }
]

Each transcript entry requires: Id (integer), Start (start time in milliseconds, integer), Speaker (string), End (end time in milliseconds, integer), Text (string).
For the Manual Upload provider, .json, .vtt, .xml, and .txt extensions are accepted and no schema validation is applied.

4. Summary: An optional pre-written or AI-generated meeting summary provided as a plain-text multipart form field named Summary.
If no recording or transcript file is uploaded, a summary must be provided.

Validation rules & errors

The API validates each request and returns the first error encountered.

Validation RuleError CodeError Message
Metadata is missing400Meeting metadata is missing. Provide metadata for meeting.
Multiple metadata fields provided400Multiple metadata for meeting are not allowed. Provide only one metadata.
Multiple summary fields provided400Multiple summary values are not allowed. Provide only one summary.
Invalid multipart form field name400Invalid form field. Only 'MetaData' and 'Summary' form fields are allowed.
Meeting title is empty400Meeting Title should not be null or empty
Meeting provider is invalid400Meeting Provider should be one of the following: Zoom, Webex, Microsoft Teams, Google Meet, Zoom Phone, Gong, Manual Upload.
MeetingStartDateTime is in the future400Meeting start date time must be less than current date time.
MeetingEndDateTime is in the future400Meeting end date time must be less than current date time.
No host participant registered in Seismic400At least one participant should be Host with a valid email registered with Seismic.
Host does not have the required entitlement400Host user does not have the required permission to manually ingest meeting.
No recording, transcript, or summary provided400Upload at least one recording or transcript file, or provide Summary 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.
Invalid file extension for the given provider400Only recording files with extension (.MP4, .MP3) and transcript files with extension (.JSON) are allowed.
Transcript JSON does not match required schema400Error occurred while transcript JSON Schema validation
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string

Meeting metadata as a JSON string. Must include Title, Provider, MeetingStartDateTime, MeetingEndDateTime, and Participants. See the description above for the full field reference and sample.

file

Meeting recording file. Supported extensions: .mp4, .mp3. Maximum file size is 2 GB.

file

Meeting transcript file. For all providers except Manual Upload, must be .json and conform to the documented transcript entry schema. For the Manual Upload provider, .json, .vtt, .xml, and .txt are accepted.

string

Optional plain-text meeting summary. Provide as a multipart form-data text field named Summary. May be supplied in place of a recording or transcript file.

Responses

Updated 8 days ago

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 8 days ago