Upload a YML feed file
Streams a Yandex Market YML feed file (plain XML or gzip, up to 500 MB and the request body limit of the Workers plan; `Content-Length` required) to storage and queues a `yml` ingest job for it, exactly like `createIngestJob` with source `yml` but for a file instead of a URL. The feed is read in resumable passes, so any number of offers works; `stats.cursor` tracks how many were consumed. The target collection is created with the products schema (name, vendor, category, category_path, price, currency, available, picture, description, url, params) when it does not exist. The file is deleted once the job is `ready`; a failed job keeps it so `retryIngestJob` can read it again.
Full-key operation
Streams a Yandex Market YML feed file (plain XML or gzip, up to 500 MB and the request body limit of the Workers plan; Content-Length required) to storage and queues a yml ingest job for it, exactly like createIngestJob with source yml but for a file instead of a URL. The feed is read in resumable passes, so any number of offers works; stats.cursor tracks how many were consumed. The target collection is created with the products schema (name, vendor, category, category_path, price, currency, available, picture, description, url, params) when it does not exist. The file is deleted once the job is ready; a failed job keeps it so retryIngestJob can read it again.
Authorization
api_key_header Every request carries an organization API key. A key has one of two scopes. A full key reaches every operation in this document and belongs on your server. A search key is the one to ship in a browser widget or a storefront page: it reaches only the operations marked x-nova-key-scope: search — searching, federated search, recommendations, event ingestion, and the visitor-facing AI operations (semantic and image search, voice transcription and voice search, assistant chat, and the visitor's own conversation). It cannot write documents or read or change configuration; any other operation answers 403. AI operations are paid in credits from the organization's wallet whichever key calls them (402 when the balance runs out), and a search key needs X-NOVA-SESSION-ID on them: the session is what a conversation belongs to, and what the per-session allowance (429) is counted against. A key of either scope may additionally carry restrictions set in the console: an allowlist of collections (403 elsewhere), a forced filter_by per collection that is ANDed into every search (document-level access control), an allowlist of fields (include_fields is limited to it and a request naming any other field in query_by, facet_by, sort_by, filter_by or highlight_fields answers 400), an IP/CIDR allowlist and an Origin/Referer allowlist (403), and a per-key rate limit (429 with Retry-After).
In: header
Query Parameters
Target collection (without tenant prefix); created if missing
Optional label shown in the console
"upsert"Value in
- "upsert"
- "create"
- "update"
- "emplace"
The file name, kept on the job for display
length <= 2048Request Body
application/octet-stream
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/ingest-jobs/upload?collection=string"{ "id": "string", "name": "string", "collection": "string", "source": "url", "status": "queued", "config": {}, "stats": { "fetched": 0, "imported": 0, "failed": 0, "cursor": 0, "passes": 0, "errors": [ { "id": "string", "error": "string" } ] }, "error": "string", "created_at": 0, "updated_at": 0, "finished_at": 0}Delete an ingest job record DELETE
Removes the job row. Does not delete documents already imported into the collection.
Retry a failed ingest job POST
Re-queues a `failed` job with its original config. Resets `stats` and `error`, and returns the job with `status: queued`. Jobs that are `queued`, `processing`, or `ready` cannot be retried.