- Bulk tasks: Process large volumes of resource or relationship operations asynchronously.
- Bundle tasks: Apply resources and relationships atomically in a single transaction.
Overview
The task API workflow consists of two main steps:- Submit a task request - Send a batch of operations using the bulk endpoints. This returns a task ID.
- Check task status - Monitor the progress and retrieve results using the task ID.
There is no way to retrieve the task ID after submitting a bulk request. Make sure to store it for later use!
At a glance
Supported bulk operations
The registry supports bulk operations for both resources and relationships:- Resource operations:
CREATE,UPSERT, orDELETEmultiple resources - Relationship operations:
CREATE,UPSERT, orDELETEmultiple relationships
Creating a bulk request
Bulk resources
Use the bulk resources endpoint to process multiple resource operations:Bulk relationships
Use the bulk relationships endpoint to process multiple relationship operations:Bundle operations
Use the bundle endpoint to process resources and relationships atomically. If any operation in the bundle fails, none of the operations are applied.Response format
A successful bulk or bundle operation returns anACCEPTED status, meaning the task is processed asynchronously in the background.
Checking task status
Whether you submitted a bulk request or a bundle operation, you can check the status of the task and eventually retrieve the results using the task endpoint.Task statuses
The overall status of the task represents the completion state of all operations in the bulk request. The possible values are:SUCCESS- All the operations of the task completed successfullyPENDING- At least one operation in the task is still pendingCANCELLED- All the operations in the task were cancelledFAILURE- At least one operations failed or was cancelled
The
CANCELLED status can only occur if the operation was cancelled by the system. There is currently
no way to cancel a task or an operation manually.For instance, if two tasks are submitted to operate on the same record id, the later task will be
kept and the earlier one will be cancelled.