activate-contract
dci activate-contract <customerID> <contractID>
Transitions a draft contract to active or scheduled (when the start date is in the future). Produces the same system state as activating via the Console.
customerID— Identifier of the resource.contractID— Identifier of the resource.
Examples
# Preview the activation without sending a request.
dci activate-contract <customer-id> <contract-id> --dry-run
# Activate a draft contract, confirmed for scripts.
dci activate-contract <customer-id> <contract-id> --yes
`status` is `active`, or `scheduled` when the start date is in the future; a `409` means an active contract of the same type already exists for this tier.
Output
OK - Contract activated or scheduled.
By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.
| Field | Type | Description |
|---|---|---|
contractId | string | The contract identifier. |
status | string | The contract status after the operation (active, scheduled, or cancelled). One of: "active", "scheduled", "cancelled". |
Raw JSON schema
{
"type": "object",
"description": "Result of an activate or cancel operation.",
"properties": {
"contractId": {
"type": "string",
"description": "The contract identifier."
},
"status": {
"type": "string",
"description": "The contract status after the operation (`active`, `scheduled`, or `cancelled`).",
"enum": [
"active",
"scheduled",
"cancelled"
]
}
}
}
Errors
On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.
HTTP status to exit code mapping
| HTTP status | Exit code | Error code | Meaning |
|---|---|---|---|
| 400 | 30 | VALIDATION_ERROR | The arguments or request body were rejected. Review the command's flags and payload. |
| 401 | 10 | AUTHENTICATION_FAILED | Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY. |
| 403 | 11 | PERMISSION_DENIED | The DoiT user or the active customer context does not have access. |
| 404 | 20 | RESOURCE_NOT_FOUND | The requested resource does not exist. Check the identifier argument. |
| 409 | 21 | RESOURCE_CONFLICT | The operation conflicts with the resource's current state. |
Related
- create-contract — Create contract
- get-contract — Retrieve a contract
- list-contracts — List contracts
- update-contract — Update contract
- cancel-contract — Cancel contract
- API reference: POST /customers/{customerID}/contracts/{contractID}/activate
Aliases: activatecontract