Project Retrieval
The project retrieval endpoint allows you to get details about a specific project using its unique ID. It provides access to project-related data, such as name, status, task count, and metadata. You can use this endpoint to integrate with the Scale API for programmatic project management and monitoring. Don’t forget to authenticate your requests with a valid API key for successful access.List All Projects
List information for all projects. Note: No parameters required. Optionally, set a boolean value forarchived to only list information for all (un)archived projects.
Create Project
The project creation endpoint enables you to programmatically create new projects on the Scale API platform. It allows automation of project creation, streamlining data annotation workflows, and efficient management of multiple projects. You need valid authentication credentials (API key) and relevant project information to use this endpoint successfully.The task type of all the tasks belonging to this project
Name identifying this project. Must be unique among all your projects. When creating tasks for this project, you should add a project: <name> parameter to the task creation request to associate the task with this project.
Whether the project being created is a Scale Rapid project. Enterprise and On-Demand customers should omit this value.
Whether the project being created is a Scale Studio project. Enterprise and On-Demand customers should omit this value.
Default parameters for tasks created under this project. Any parameters specified here will be set if omitted in a task request; they will be overridden by any values sent in the task request. params.instruction behaves slightly differently; values here will instead be appended after the task-level instruction.
Studio projects only. Specify the pipeline of the project. Must use either standard_task or consensus_task.
Studio consensus projects only. Specify the number of attempts
Update Project Parameters
You can set parameters on a project. Project-level-parameters will be set on future tasks created under this project if they are not set in the task request. Any parameters specified in the task request will override any project parameter. Projects keep a history of the parameters that they were set with. Tasks created under a project inherit the latest params of the project (the last entry in param_history), one can also specify project_version when creating a task to inherit from an older set of params (or use -1 to skip parameter inheritance altogether.) Tasks have a**project_param_version** field pointing to the project version in place at the time a task was created.
If you haven’t already, check out our guide to using Project-level parameters to learn more about how this workflow comes togeher.
Just want to see some examples? We’ve added those as well.
When generating the newest set of project parameters, whether or not to combine the most recent project parameters with the parameters specified in this request. Defaults to false. For example, if the current params contains { instruction: ‘label the cats in the image’ } and the latest call to this API contains the task parameter { objects_to_annotate: [‘cat’] }, whether or not patch is additionally set will determine if the new project parameters also contain the instruction “label the cats in the image”. Note that any fields set in the API request completely override any fields from the previous version; object or array values will not be merged.
instruction field to combine with any specified task-level instruction.
Default parameters for tasks created under this project. Any parameters specified here will be set if omitted in a task request; they will be overridden by any values sent in the task request.