Ingest Legacy
POST /ingest is a compatibility endpoint for direct post_video queue-item ingestion.
account_id + content_id.
Request Example
Accepted Response
Duplicate Response
Request Fields
| Field | Type | Required | Notes |
|---|---|---|---|
content_id | string | yes | Caller content identifier. |
account_id | string | yes | Active target account id. |
video_path | string | yes | Must be a valid http(s) asset URL. |
caption | string | yes | Max length 4000. |
hashtags | string[] | no | Optional hashtags list. |
sound_id | string or null | no | Optional sound id. |
cover_image_path | string or null | no | Must be a valid http(s) asset URL when provided. |
callback_url | string or null | no | Optional per-item callback URL. |
scheduling_hint | string or null | no | Must parse as ISO-8601 when provided. |
metadata | object | no | Free-form metadata. Defaults to {}. |
Validation Rules
video_pathmust be validhttp(s).cover_image_pathmust be validhttp(s)when present.- assets are
HEAD-checked before enqueue captionmust be non-empty and at most4000charactersaccount_idmust resolve to an active account
Idempotency
Idempotency key:Failure Modes
| Status code | Meaning |
|---|---|
401 | Missing or invalid bearer token. |
404 | Account not found or inactive. |
422 | Invalid payload, invalid URL, missing asset, or invalid timestamp. |
500 | Unexpected enqueue failure. |