/v1/experimentCreate experiment
Create a new experiment. If there is an existing experiment in the project with the same name as the one specified in the request, will return the existing experiment unmodified
- IdempotentThe SDK sends
Idempotency-Key, so a retried request is only applied once.
Any desired information about the new experiment object
Unique identifier for the project that the experiment belongs under
Name of the experiment. Within a project, experiment names are unique
Textual description of the experiment
Metadata about the state of the repo when the experiment was created
Id of default base experiment to compare against when viewing this experiment
Identifier of the linked dataset, or null if the experiment is not linked to a dataset
Version number of the linked dataset the experiment was run against. This can be used to reproduce the experiment after the dataset has been modified.
Whether or not the experiment is public. Public experiments can be viewed by anybody inside or outside the organization
User-controlled metadata about the experiment
Normally, creating an experiment with the same name as an existing experiment will return the existing one un-modified. But if ensure_new is true, registration will generate a new experiment with a unique name in case of a conflict.
Unique identifier for the experiment
Unique identifier for the project that the experiment belongs under
Name of the experiment. Within a project, experiment names are unique
Textual description of the experiment
Date of experiment creation
Metadata about the state of the repo when the experiment was created
Commit, taken directly from repo_info.commit
Id of default base experiment to compare against when viewing this experiment
Date of experiment deletion, or null if the experiment is still active
Identifier of the linked dataset, or null if the experiment is not linked to a dataset
Version number of the linked dataset the experiment was run against. This can be used to reproduce the experiment after the dataset has been modified.
Whether or not the experiment is public. Public experiments can be viewed by anybody inside or outside the organization
Identifies the user who created the experiment
User-controlled metadata about the experiment
A 400 is returned: The request was unacceptable, often due to missing a required parameter A 401 is returned: No valid API key provided A 403 is returned: The API key doesn’t have permissions to perform the request A 429 is returned: Too many requests hit the API too quickly. We recommend an exponential backoff of your requests A 500 is returned: Something went wrong on Braintrust's end. (These are rare.)