get_project
Read one project's detail document: identity, base URL, execution target, and the configured test site URLs.
Request
GET /api/v1/ops/projects/{project}
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
project | path | string | yes | The project's public id. |
- cURL
- CLI
- MCP
curl -H "Authorization: Bearer $TESTVIBE_API_KEY" \
"$TESTVIBE_SERVER/api/v1/ops/projects/$PROJECT"
testvibe project
Tool get_project — optional project.
Response
{
"id": "a1b2c3d4-…",
"name": "Demo Shop",
"baseUrl": "https://demo.example",
"executionTarget": "sandbox",
"testSiteUrls": [
{ "url": "https://demo.example", "isDefault": true },
{ "url": "https://staging.demo.example", "isDefault": false }
]
}
testSiteUrls are the candidate targets for the siteUrl override on run_feature, run_suite, and generate_feature; the default one is used when no override is given.
Errors
| HTTP | When |
|---|---|
404 not_found | No such project in this workspace. |
The document can additionally include optional expectTimeoutMs, testTimeoutMs, targetConcurrency, retryFailed, and generationTimeoutMinutes, plus browser context metadata. testSiteUrls entries can have a friendly label. Sensitive browser-auth passwords are not returned. Inspect executionTarget as returned; it is not a promise of a public runner-registration API.
Update supported project settings with PATCH /api/v1/ops/projects/{project}. expectTimeoutMs clamps positive values to 1,000–120,000 (0/null clears to the 30,000 default); testTimeoutMs to 15,000–600,000 (0/null clears to 300,000); generationTimeoutMinutes to 5–120 (0/null clears to 60); targetConcurrency to 1–64 (0/null clears); retryFailed to 0–3 (null clears). CLI exposes testvibe project --expect-timeout <ms> --test-timeout <ms>; MCP provides set_expect_timeout and set_test_timeout.