Evaluation sets are collections of files and expected outputs that are used to evaluate the performance of a given extractor, classifier, or splitter. This endpoint will create a new evaluation set, which items can be added to using the Create Evaluation Set Item endpoint.
Note: It is not necessary to create an evaluation set via API. You can also create an evaluation set via the Extend dashboard and take the ID from there. To learn more about how to create evaluation sets, see the Evaluation Sets product page.
Bearer authentication of the form Bearer <token>, where token is your auth token.
The name of the evaluation set.
Example: "Invoice Processing Test Set"
The ID of the extractor, classifier, or splitter to create an evaluation set for. Evaluation sets can in theory be run against any extractor, classifier, or splitter, but it is required to associate the evaluation set with a primary extractor, classifier, or splitter.
Example: "ex_Xj8mK2pL9nR4vT7qY5wZ"
A description of what this evaluation set is used for.
Example: "Q4 2023 vendor invoices"
The type of object. In this case, it will always be "evaluation_set".
The ID of the evaluation set.
Example: "ev_2LcgeY_mp2T5yPaEuq5Lw"
The name of the evaluation set.
Example: "Invoice Processing Test Set"
A description of the evaluation set.
Example: "Q4 2023 vendor invoices for accuracy testing"
The time (in UTC) at which the object was created. Will follow the RFC 3339 format.
Example: "2024-03-21T16:45:00Z"
The time (in UTC) at which the object was last updated. Will follow the RFC 3339 format.
Example: "2024-03-21T16:45:00Z"
API version to use for the request. If you’re using an SDK, you can ignore this parameter. If you are not using an SDK and do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.