Delete an ingest job record
Removes the job row. Does not delete documents already imported into the collection.
Операция для полного ключа
Removes the job row. Does not delete documents already imported into the collection.
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
Path Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/ingest-jobs/string"{ "id": "string"}Get ingest job status GET
Upload status for a document ingest job. Poll until `status` is `ready` or `failed`. Terminal jobs include `stats.fetched` / `imported` / `failed` and optional `error`.
Upload a YML feed file POST
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.