curl --request GET \
--url https://api.callva.io/api/v1/external/presets \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.callva.io/api/v1/external/presets"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.callva.io/api/v1/external/presets', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"success": true,
"message": "Presets retrieved successfully",
"data": [
"<unknown>"
]
}{
"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": "<string>"
}List the preset catalogue
Requires permission: dashboard.read.
What a token may call depends on its role: see Authentication and permissions.
Every preset descriptor the platform offers, fully resolved.
Read-only, and the same answer for every caller in a deployment: the descriptors are platform vocabulary and carry no tenant data, which is why this sits on the narrowest surface that serves it rather than inside a project context it does not need.
Served whole - resolves_to, consumed_by and the authoring notes
included - rather than projected down to what today’s form happens to
read. A projection here would be a second hand-maintained copy of the
descriptor, which is the failure this registry exists to remove.
Retired presets are served too, marked retired: an agent still on one
has to be able to name it, and the form decides what to offer.
Cacheable: the body changes only when a descriptor on disk changes, so it carries an ETag over its own content and answers 304 to a caller that already has it.
curl --request GET \
--url https://api.callva.io/api/v1/external/presets \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.callva.io/api/v1/external/presets"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.callva.io/api/v1/external/presets', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"success": true,
"message": "Presets retrieved successfully",
"data": [
"<unknown>"
]
}{
"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": "<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.