Generate dataset configuration from specifications
Derives dataset type, variant, and name from specifications (rule-based).
With automaticCreation: true this does more than return a suggestion: it creates the datasets and their test-case generation continues on the background worker, so each one comes back with status PENDING.
Accuracy (QUALITY) specifications need groundTruthUri, a knowledge base file uploaded beforehand, because an accuracy dataset grades answers against known-correct ones and a specification never states what the correct answer is.
See Datasets.
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
IDs of the specifications to generate dataset configs for
1When true, creates the datasets from the generated config and starts their test-case generation on the background worker.
false
How many test cases to generate per dataset. Defaults to 3. The upper limit is per test type and deployment-configured, and is enforced when the dataset is created (automaticCreation: true).
x > 030
Presigned upload URL of the knowledge base file, uploaded beforehand. Required for accuracy (QUALITY) specifications, ignored for the other test types.
Response
Dataset configuration generated, and the datasets created when asked for