Batch endpoints allow you to perform bulk create, update, and delete operations in a single API call, avoiding the overhead of many individual requests.
Available Batch Endpoints #
| Endpoint | Description |
|---|---|
POST /wp-json/dmsi-api/v1/batch/customers | Bulk create, update, or delete customers |
POST /wp-json/dmsi-api/v1/batch/licenses | Bulk license operations |
POST /wp-json/dmsi-api/v1/batch/activations | Bulk activation operations |
POST /wp-json/dmsi-api/v1/batch/subscriptions | Bulk subscription operations |
GET /wp-json/dmsi-api/v1/batch/jobs/{job_id} | Poll the status of a long-running batch job |
How Batch Jobs Work #
When a batch request contains a large number of items or long-running operations, the API returns a job_id instead of processing synchronously. Poll the job status endpoint to check progress and retrieve results.
{
"data": {
"job_id": "job_xyz789",
"status": "pending"
},
"meta": {
"request_id": "req_abc123",
"version": "1.0.1",
"environment": "production",
"timestamp": "2026-03-31T00:00:00Z"
}
}
Scope Requirements #
Batch operations require the same scopes as their individual equivalents. A batch license operation requires the licenses:write or licenses:delete scope depending on the operations included in the batch payload.