Operation
Update inventory capacity
PATCH
/inventory/{id}/capacityUpdate the total capacity of an inventory bucket
Path parameters
idstringRequired- Inventory ID
Headers
Idempotency-KeystringOptional- Makes the write safe to retry. The first request with a key does the work and its response is stored for 24 hours; a repeat with the same key and the same request (method, path, query, X-Ticketlayer-Channel, TL-Version and body) gets that stored status and body back, marked `Idempotent-Replay: true`, without running again. The key is scoped to your organisation and your credential. The same key with a different request is 422 IDEMPOTENCY_KEY_REUSED; a repeat while the first is still running waits for it, then answers 409 IDEMPOTENT_REQUEST_IN_PROGRESS if it has not finished. Only a 2xx is stored: after an error the key is free again. Omit the header and the request behaves as it always has.
Body
totalCapacity*integerNew total capacity
accountId*stringAccount ID
Returns
Inventory capacity updated successfully
Errors
- 400
- Bad Request - Invalid input
- 401
- Unauthorized - Authentication required
- 403
- Forbidden - Insufficient permissions
- 404
- Not Found - Resource not found
- 500
- Internal Server Error
Every error names its code and links to it. All error codes
curl -X PATCH "https://api.ticketlayer.com/v1/inventory/inv_abc123/capacity" \ -H "Authorization: Bearer tlak_..." \ -H "X-Ticketlayer-Org: your-org-slug" \ -H "Content-Type: application/json" \ -d '{ "totalCapacity": 150, "accountId": "acc_def456" }'Response 200
{
"inventory": {
"id": "inv_abc123",
"organisationId": "org_xyz789",
"accountId": "acc_def456",
"sourceType": "event_occurrence_area",
"eventId": "evt_ghi789",
"eventOccurrenceId": "evo_jkl012",
"eventLayoutAreaId": "ela_mno345",
"productId": "prd_pqr678",
"totalCapacity": 500,
"available": 450,
"reserved": 30,
"confirmed": 20,
"held": 0,
"isAllocated": false,
"version": 1,
"metadata": null,
"createdAt": "2024-12-28T10:30:00Z",
"updatedAt": "2024-12-28T14:45:00Z"
}
}