Skip to main content
POST
Import a transcript
Import a meeting or interview transcript. Behaves exactly like POST /v1/import with one extra target_speaker form field naming whose turns the import should focus on, so only that speaker’s contributions land in the subject’s knowledge graph. Send the file as multipart/form-data.

Authorization

This route requires the write scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Notes

  • target_speaker is the whole point of this route. It names whose turns to keep, so an interview does not enter the graph as if the subject had said everything in it.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Body

multipart/form-data
file
string
required
target_speaker
string
required

Response

The accepted import job.

202 response for /v1/ingest and /v1/import: the durably-queued job.

jobId
string
required
status
string
default:pending