curl --request POST \
--url https://api.callva.io/api/v1/external/agents/{id}/presets/{preset}/activate \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.callva.io/api/v1/external/agents/{id}/presets/{preset}/activate"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text)const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.callva.io/api/v1/external/agents/{id}/presets/{preset}/activate', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"success": true,
"message": "Preset activated successfully",
"data": {
"agent_id": "<string>",
"preset": "<string>"
}
}{
"success": true,
"message": "Project context required"
}{
"error": "Invalid or expired token",
"message": "The provided token is invalid or has expired"
}{
"success": true,
"message": "Insufficient permission.",
"code": "insufficient_permission"
}{
"success": true,
"message": "Agent not found"
}{
"success": true,
"message": "Validation failed",
"errors": {
"preset": [
"<string>"
]
}
}{
"success": true,
"message": "<string>"
}Activate an agent's preset
Requires permission: agents.update.
What a token may call depends on its role: see Authentication and permissions.
Make this preset the one the agent’s next call runs on.
Selecting a preset is activation - there is no separate confirming act, and a selection made mid-day changes live behaviour immediately.
Activation creates no row. An agent whose named preset has no row compiles on the registry’s defaults, which is what lets a preset be selected before it has been configured.
A retired preset is refused with 422 and the name of its replacement, unless it is the one the agent already runs.
curl --request POST \
--url https://api.callva.io/api/v1/external/agents/{id}/presets/{preset}/activate \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.callva.io/api/v1/external/agents/{id}/presets/{preset}/activate"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text)const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.callva.io/api/v1/external/agents/{id}/presets/{preset}/activate', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"success": true,
"message": "Preset activated successfully",
"data": {
"agent_id": "<string>",
"preset": "<string>"
}
}{
"success": true,
"message": "Project context required"
}{
"error": "Invalid or expired token",
"message": "The provided token is invalid or has expired"
}{
"success": true,
"message": "Insufficient permission.",
"code": "insufficient_permission"
}{
"success": true,
"message": "Agent not found"
}{
"success": true,
"message": "Validation failed",
"errors": {
"preset": [
"<string>"
]
}
}{
"success": true,
"message": "<string>"
}Authorizations
A CallVA API token, sent as Authorization: Bearer <token>.
Creating one. In the CallVA dashboard, open the organization's Settings, then API Keys, and choose Create API Key: give the key a name, choose its role, and choose its project scope - All projects for an organization-wide token, or one project for a project token. The key is shown once, when it is created, and cannot be read again; store it then. Creating keys needs the api_tokens.create permission, which owners and admins hold, and a key cannot create another key.
Organization-wide or project token. A project token works in the one project it was created for; any project named in the request is ignored. An organization-wide token reaches the projects of its organization, and each request names its project with the X-Project-ID header or project_id (query string for reads and deletes, body for writes).
What it can call. The token's role decides which endpoints it may call; each endpoint names the permission it requires, and a token whose role lacks it is answered 403.
Headers
The project this request acts in. Required with an organization-wide token (or send project_id instead); ignored with a project token, which always acts in its own project.