artifact ID.
Artifacts can be created from:
Prerequisites
- An API token with the required write scope. See Backoffice Developer Console or Token Management.
- Your Zylon hostname (replace
{BASE_URL}in the examples).
Basic request and response
UsePOST /artifacts/ingest when you want the ingest to complete in the same request.
Example response
Example response
Sync ingest response fields
Sync ingest response fields
Nullable fields may be omitted. Arbitrary upstream document metadata is not included in the synchronous ingest response.
Async ingest
UsePOST /artifacts/ingest/async for larger payloads or when ingest may take longer. Wrap the sync ingest payload in ingest_body and include the required callback object. Use callback: {} when polling without callback configuration. The response returns a task_id you can poll.
Endpoint parameters
Endpoint parameters
- Text
- File
- URI
Example response
Example response
Example response
Example response
Listing ingested artifacts
Example response
Example response
Retrieving content
Full content
UsePOST /artifacts/content to fetch complete document text:
Example response
Example response
Chunked content (chat-optimized)
UsePOST /artifacts/chunked-content to retrieve content split into chat-friendly blocks:
Example response
Example response
Deleting artifacts
Delete (sync):Example response
Example response
Example response
Example response
Example response
Example response
Errors and edge cases
- 401/403: missing token or insufficient permissions.
- 404: collection or artifact not found.
- 409: ingest/delete task already in progress.
- 413: input too large for a single ingest.
- 422: invalid payload shape.
- Async failures: when
task_statusbecomesFAILURE, checktask_result(for examplerouting_key_error: "ingest.failed"ordelete.failed) and retry after fixing the input.