runs

Ingest Runs (Multipart)

Changed on

Ingests multiple runs, feedback objects, and binary attachments in a single multipart/form-data request. Part‑name pattern: <event>.<run_id>[.<field>] where event ∈ {post, patch, feedback, attachment}.

  • post|patch.<run_id> – JSON run payload.
  • post|patch.<run_id>.<field> – out‑of‑band run data (inputs, outputs, events, error, extra, serialized).
  • feedback.<run_id> – JSON feedback payload (must include trace_id and session_id).
  • attachment.<run_id>.<filename> – arbitrary binary attachment stored in S3. Headers: every part must set Content-Type and either a Content-Length header or length parameter. Per‑part Content-Encoding is not allowed; the top‑level request may be Content-Encoding: gzip or Content-Encoding: zstd. Best performance for high‑volume ingestion.
post/api/v1/runs/multipart

Request

  • Base URL
    https://api.smith.langchain.com
  • URL
    https://api.smith.langchain.com/api/v1/runs/multipart
  • Auth
    • API key in header X-API-Key
    • or API key in header X-Tenant-Id
    • or HTTP bearer

Request body multipart/form-data

post.{run_id}string binary

Run to create (JSON)

patch.{run_id}string binary

Run to update (JSON)

post.{run_id}.inputsstring binary

Large inputs object (JSON) stored out‑of‑band

patch.{run_id}.outputsstring binary

Large outputs object (JSON) stored out‑of‑band

feedback.{run_id}string binary

Feedback object (JSON) – must include trace_id and session_id

attachment.{run_id}.{filename}string binary

Binary attachment linked to run {run_id}

Response

Accepted

object required

Changes

  • 1a8ee9358d81Revision changes
    • breaking

      added required request body

    • breaking

      the response's body type changed from no type to object for status

    • info

      api operation id create_runs_multipart_proxy_api_v1_runs_multipart_post removed and replaced with

    • info

      api tag runs added

    • info

      api tag run removed

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

  • a0acb3a6a101Revision changes
    • info

      endpoint added