Sign in

v29

latestOpenAPI 3.1.0raw.githubusercontent.com2026-03-233765161.7 KB
v1 data

Confirm a signed-URL upload and start processing

Step 2 of 2 — After uploading the file to the signed URL obtained from /ingest/upload-url, call this endpoint to trigger the ingest pipeline.

The server verifies the file exists in GCS, auto-detects the content type
if it was not provided, and queues the processing job.

Returns the same `IngestResponse` as the regular `/ingest` endpoint.
post/v1/data/ingest/confirm-upload

Request body

job_idstring required

Job ID returned by /ingest/upload-url

object_keystring required

GCS object key returned by /ingest/upload-url

user_idstring required

User ID (must match the upload-url request)

persona_idstring nullable
project_idstring nullable
content_typestring nullable

Content category (auto-detected from file bytes if omitted)

content_descriptionstring nullable
session_idstring nullable
timestampstring nullable
filenamestring nullable
callback_urlstring nullable

Optional URL the server will POST to when the job reaches a terminal state.

notification_emailstring email nullable

Optional email address to notify when the job reaches a terminal state.

Response

Successful Response

job_idstring required

Unique job identifier for tracking

statusstring required

Processing status ('accepted', 'queued', 'failed')

messagestring nullable

Additional status or error message

successboolean

Whether the request was accepted successfully

Example response

{
  "content_type": "text",
  "created_at": "2024-01-01T12:00:00Z",
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "message": "Content successfully uploaded and queued for processing",
  "status": "queued",
  "success": true,
  "user_id": "abc-123"
}