List workspace budgets
The organization's total daily warmup cap (orgLimit; null means unlimited, not zero), how much of it is allocated, and each workspace's dailyWarmupBudget. Requires a personal (ti_pk_) key whose creator is an organization owner.
curl -X GET "https://lynx-api.trulyinbox.com/v2/workspaces/quotas"{
"data": {
"orgLimit": 0,
"allocated": 0,
"workspaces": [
{
"workspaceId": 0,
"workspaceName": "string",
"dailyWarmupBudget": 0
}
]
},
"meta": {
"request_id": "req_2f1c…",
"timestamp": "2019-08-24T14:15:22Z"
}
}{
"error": {
"code": "invalid_request",
"message": "string",
"details": {},
"retry_after": 34
},
"meta": {
"request_id": "req_2f1c…",
"timestamp": "2019-08-24T14:15:22Z"
}
}{
"error": {
"code": "invalid_request",
"message": "string",
"details": {},
"retry_after": 34
},
"meta": {
"request_id": "req_2f1c…",
"timestamp": "2019-08-24T14:15:22Z"
}
}Create a workspacePOST
Provisions a new workspace in the organization - one per end-customer for a partner integration. Requires a personal (`ti_pk_`) key whose creator is an organization owner; a workspace-scoped key is rejected. Every organization owner, the key creator included, becomes an owner of the new workspace. The key acts as its creator and stops working if they leave or stop being an owner, so use a key owned by a service account rather than an individual. Pass `dailyWarmupBudget` to allocate the new workspace its daily warmup budget in the same call; that field also needs the `workspace:quota` scope.
Update workspace budgetsPATCH
Sets `dailyWarmupBudget` for the listed workspaces only; every other workspace keeps its budget. The organization's cap is checked once across the whole request, before anything is written, so one call can move budget between workspaces (lower one, raise another) even when the organization is fully allocated. A lowered budget applies immediately: a workspace that has already sent more today than its new budget stops for the rest of the day. Requires a personal (`ti_pk_`) key whose creator is an organization owner.