Create a job
A JOB
POST
https://api.playment.io/v1/projects/:project_id/jobs
This endpoint allows you to create a job
Path Parameters
Name | Type | Description |
---|---|---|
project_id | string | ID of the project in which you want to create the job |
Headers
Name | Type | Description |
---|---|---|
x-api-key | string | API key for authentication |
Request Body
Name | Type | Description |
---|---|---|
batch_id | string | A batch is a way to organize multiple jobs under one |
work_flow_id | string | The ID of the workflow inside which you want to create the job |
data | object | The |
reference_id | string | Your unique identifier for the job. We suggest you use a UUID or incremental counter such that each job has a unique reference_id |
After creating the job, please store the job_id
received in the response. You'll use this job_id
to get the annotations later.
Body Parameters
Project ID
After opening a project, You can find the project_id
in the information tooltip or URL.
Workflow ID
Batch ID
In the Batches section of a project, You can find the batch_id
in the batch information tooltip.
Payload
The payload data structure varies depending on the type of task
Image Annotation & Image Segmentation
Video Annotation
Attachment Access
The attachments you pass in the job creation requests ultimately need to be made available to the annotators who make the annotations in GT Studio. Depending on the type of workforce and whether you agree to give Playment access to your data, there are a couple of methods through which you can provide access to these attachments:
Workforce Type | Playment can access? | Method |
Managed by Playment | Yes | |
Not managed by Playment | Yes | |
Not managed by Playment | No |
Errors
For details on possible errors, please follow this link:
pageError CodesLast updated