Create test
Create a new test. See Tests.
File uploads. The uri, groundTruthUri, and dataCatalogUri fields of TestInput
each expect a presigned GET URL (S3 X-Amz-* or Azure Blob SAS) for a file that was
already uploaded via the storage PUT-presign endpoint. The server strips the signing
query and persists the underlying storage URI (s3://<bucket>/<key> for S3, or the
query-less blob URL for Azure) on the created test.
Providing uri switches the request into “custom test file” mode: generation is
skipped, the test is created in SUCCESS state, and credit checks / maxTestCases
/ generator-specific validations are bypassed.
Documentation Index
Fetch the complete documentation index at: https://docs.galtea.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
API key authorization. Pass your API key in the Authorization header as a Bearer token. Both new (gsk_*) and legacy (gsk-) API keys are accepted, e.g. Authorization: Bearer gsk_... or Authorization: Bearer gsk-....
Body
Test data
Product ID
"prod_123"
Test name
"Quality Test"
QUALITY, RED_TEAMING, SCENARIOS "QUALITY"
Specification ID (can auto-derive type/variants)
"spec_123"
Presigned GET URL (S3 X-Amz-* query or Azure Blob SAS) for a ground-truth file previously uploaded via the storage PUT-presign endpoint. The server strips the signing query and persists the underlying storage URI. Cannot be combined with sourceTestId.
"https://my-bucket.s3.amazonaws.com/tests/ground-truth.csv?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=...&X-Amz-Signature=..."
Presigned GET URL for a fully prepared custom test file previously uploaded via the storage PUT-presign endpoint. When provided, no test-case generation runs: the file is ingested as-is, the test is created in SUCCESS state, and maxTestCases, generator-related fields, and credit checks are skipped. Cannot be combined with sourceTestId or dataCatalogUri. Must be non-empty.
"https://my-bucket.s3.amazonaws.com/tests/test.csv?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=...&X-Amz-Signature=..."
Optional few-shot examples used to guide test-case generation for QUALITY tests.
"Q: What is 2+2? A: 4"
"en"
Test variants. QUALITY: rag, entity_extraction, summarization, classification, translation, correction, other. RED_TEAMING: data_leakage, financial_attacks, illegal_activities, misuse, toxicity, custom.
["rag"]Custom variant description
"Custom test variant"
Generation strategies. "original" is the default for RED_TEAMING. At least one strategy is required for SCENARIOS tests.
["original"]"Business analyst"
100
SCENARIOS only. Maximum number of conversation turns per generated scenario when scenario generation is executed. If omitted, the scenario-generator default is used. If uri is provided, no scenario generation runs, so this field is ignored at test-creation time. When generation runs, the value is forwarded to the scenario-generator and persisted on each generated test case. Ignored for QUALITY and RED_TEAMING tests.
x >= 110
["gpt-4"]Source QUALITY test ID whose approved test cases seed a SCENARIOS test. Only valid when type = SCENARIOS. Cannot be combined with uri or groundTruthUri.
"test_123"
Presigned GET URL for a data-catalog file previously uploaded via the storage PUT-presign endpoint. Only valid when type = SCENARIOS. Cannot be combined with uri.
"https://my-bucket.s3.amazonaws.com/tests/data-catalog.json?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=...&X-Amz-Signature=..."
Arbitrary key-value metadata
{ "key": "value" }Response
Test created successfully
"test_123"
"prod_123"
"user_123"
"Quality Test"
QUALITY, RED_TEAMING, SCENARIOS "QUALITY"
Canonical storage URI of the ground-truth file, derived from the presigned URL supplied at creation. S3: s3://<bucket>/<key>. Azure Blob: blob URL with the SAS query stripped (e.g. https://<account>.blob.core.windows.net/<container>/<path>).
"s3://my-bucket/tests/test_123/ground-truth.csv"
Canonical storage URI of the uploaded custom test file. Same format rules as groundTruthUri.
"s3://my-bucket/tests/test_123/test.csv"
PENDING, SUCCESS, FAILED, AUGMENTING "SUCCESS"
Optional few-shot examples (input/output pairs) used to guide test-case generation for QUALITY tests.
"Example few-shot learning data"
"en"
Test variants. QUALITY: rag, entity_extraction, summarization, classification, translation, correction, other. RED_TEAMING: data_leakage, financial_attacks, illegal_activities, misuse, toxicity, custom.
["rag", "summarization"]"Custom variant description"
Generation strategies. "original" is the default for RED_TEAMING. At least one strategy is required for SCENARIOS tests.
["original"]"Business analyst"
100
["gpt-4", "claude-3"]Canonical storage URI of the data-catalog file (SCENARIOS tests only). Same format rules as groundTruthUri.
"s3://my-bucket/tests/test_123/data-catalog.json"
{ "key": "value" }"spec_123"