QAVE Studio suite fetch API
Project SDK keys and paginated /sdk routes for listing approved suites and cases.
External Assurance SDK runners fetch approved suites and cases from QAVE Studio. Create a project SDK API key in Studio Settings → Project SDK API keys (shown once). The same page shows the project ID with a copy control — you need both the key and the project ID for /sdk paths.
Auth
Authorization: Bearer qave_sdk_...The key is scoped to one project. The project_id in the path must match the key or the API returns 403.
List approved suites
GET /sdk/projects/{project_id}/test-suites?page=1&page_size=50Default page_size is 50; max is 200.
{
"items": [
{
"id": "…",
"name": "Checkout happy path",
"description": null,
"status": "APPROVED",
"metadata": {},
"created_at": "…",
"updated_at": "…"
}
],
"page": 1,
"page_size": 50,
"total": 1
}Only APPROVED suites are returned.
Fetch approved cases
GET /sdk/projects/{project_id}/test-suites/{suite_id}/cases?page=1&page_size=50Default page_size is 50; max is 100. Unknown or non-approved suites return 404. Only APPROVED cases are included. Loop page until you have total rows.
Each case is the full stored record (id, conversation_history, criteria, title, intent, dimension_snapshot, …). Map conversation_history to messages in the runner if needed.
Studio key APIs (JWT)
| Method | Path |
|---|---|
GET | /projects/{project_id}/sdk-keys |
POST | /projects/{project_id}/sdk-keys { "name": "optional" } |
DELETE | /projects/{project_id}/sdk-keys/{key_id} |
POST returns api_key once. Revoke immediately disables /sdk access.