Async ingestion
For large files or batches, use the async endpoints to avoid holding the HTTP connection open. Jobs are processed by a background worker (Celery) and can be polled for status.
Async jobs require a Celery worker running alongside the API server. Start one with make celery.
This feature requires to have the worker extra enabled in your application. If you are adding storage to an existing application, make sure to run the sync command after enabling the module:
Lifecycle
Async ingest
Response:
Poll for status
Response:
Status values: PENDING · SUCCESS · FAILURE · REVOKED
Poll until task_status is SUCCESS or FAILURE.
Async delete
Worker setup
The broker is configured in settings.yaml under celery.broker_mode. Supported options: redis, rabbitmq, local.

