curl --request PATCH \
--url https://api.callva.io/api/v1/external/calls/batch \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"updates": "<string>"
}
'import requests
url = "https://api.callva.io/api/v1/external/calls/batch"
payload = { "updates": "<string>" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.patch(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'PATCH',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({updates: '<string>'})
};
fetch('https://api.callva.io/api/v1/external/calls/batch', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"success": true,
"message": "Calls updated successfully",
"data": {
"updated_count": 1,
"ids": "<string>"
}
}{
"success": false,
"message": "This API token is tenant-scoped. Please provide project_id in the request payload or query parameters, or use a project-scoped token.",
"code": "PROJECT_REQUIRED"
}{
"error": "Invalid or expired token",
"message": "The provided token is invalid or has expired"
}{
"success": false,
"message": "Insufficient permission.",
"code": "insufficient_permission"
}{
"success": true,
"message": "Validation failed",
"errors": {}
}{
"success": true,
"message": "Failed to update calls"
}Update calls in bulk
Requires permission: calls.update.
What a token may call depends on its role: see Authentication and permissions. Guide: Calls and outbound dispatch.
Apply one set of field values to a list of calls, all or nothing.
updates is validated with the same definition-derived rules as
single-call update, and a key the project does not define is refused
rather than silently dropped. Ids resolve through the tenant- and
project-scoped Call query, so an id from elsewhere is named in the
errors instead of passing an unscoped exists check and being skipped.
curl --request PATCH \
--url https://api.callva.io/api/v1/external/calls/batch \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"updates": "<string>"
}
'import requests
url = "https://api.callva.io/api/v1/external/calls/batch"
payload = { "updates": "<string>" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.patch(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'PATCH',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({updates: '<string>'})
};
fetch('https://api.callva.io/api/v1/external/calls/batch', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"success": true,
"message": "Calls updated successfully",
"data": {
"updated_count": 1,
"ids": "<string>"
}
}{
"success": false,
"message": "This API token is tenant-scoped. Please provide project_id in the request payload or query parameters, or use a project-scoped token.",
"code": "PROJECT_REQUIRED"
}{
"error": "Invalid or expired token",
"message": "The provided token is invalid or has expired"
}{
"success": false,
"message": "Insufficient permission.",
"code": "insufficient_permission"
}{
"success": true,
"message": "Validation failed",
"errors": {}
}{
"success": true,
"message": "Failed to update calls"
}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.