Playment: API Developer Docs

The Playment Developer Hub

Welcome to the Playment developer hub.
Here, You'll find comprehensive documentation & examples to help you start working with Playment as quickly as possible, and get support if you get stuck.

Get Started

Playment API

Integrate Playment's API with your workflow to leverage the intelligence of thousands of humans whenever you want

 

Get Started

You just need to send us the data. We take care of everything else.

Check out the documentation below to see how easy it is to use the API.

You can check out these examples to see how other developers are utilising the Playment API.

Contact us at hello@playment.in to get started.

Creating a request

 

A request represents one piece of work that you would want our workers to do for you.

Hit our Feedline API to create a request, or what we call, a feed line unit (FLU)

Create Feed Line Unit

POST https://staging-api.playment.in/v1/project/ project_id /feedline *
POST https://api.playment.in/v1/project/ project_id /feedline

Parameters

project_id : To be passed in the url
x-client-key : Secret key to be passed as a header

* We'll share the project_id and x-client-key separately with you via a secure channel

Payload

{  
   "reference_id":"001",
   "data":{  
      "image_url":[  
         "https://dummyimage.com/600x400/000/fff.jpg&text=Dummy+Image+1",
         "https://dummyimage.com/600x400/000/fff.jpg&text=Dummy+Image+2",
         "https://dummyimage.com/600x400/000/fff.jpg&text=Dummy+Image+3"
      ]
   },
   "tag":"categorise_image"
}

Check out the examples below to see different types of request structures.

x-client-key

Each request requires authentication with an API-key (x-client-key) which we verify before accepting a request.

reference_id

reference_id is a unique identifier for a request. We'll fail a request if you've sent another request with the same reference_id previously. This helps us ensure that we don't charge you for work which we've already done for you.

tag

Each request should have a tag which tells us what operation needs to be performed on that request. We'll share this tag with you during the integration process.

QPS

The API currently supports up to 20 requests per second.

Error Codes

FS_0001

Duplicate Reference Id

FS_0002

Reference Id Missing

FS_0003

Invalid Data Passed

FS_0004

Data missing

FS_0005

Tag Missing

FS_0006

Feed Line Unit not found

FS_0007

Image urls not valid

GE_0001

Malformed JSON/Invalid UUID passed

GE_0002

Parameter missing

Sample requests & responses

With error cases

 
{
	"reference_id": "reference_1",
	"data": {
		"image_url": ["URL_1", "URL_2"],
		"image_secondary": "URL_3"
	},
	"tag": "image_qc"
}
{
	"data": {
		"image_url": ["URL_1", "URL_2"],
		"image_secondary": "URL_3"
	},
	"tag": "image_qc"
}
{
	"reference_id": "reference_1",
	"data": {
		"image_url": ["URL_1", "URL_2"],
	},
	"tag": "image_qc",
}
{
	"reference_id": "reference_1",
	"data": {
		"image_url": 1234,
	},
	"tag": "image_qc"
}
{
	"feed_line_unit": {
		"flu_id": "33abc3fe-9fbc-4d7c-b951-a1d1bfb6f80",
		"reference_id": "ref_id_1",
		"tag": "image_qc"
	},
	"success": true
}
{
  "error": {
    "code": "FS_0002",
    "message": "Reference Id Missing"
  },
  "success": false
}

{
  "error": {
    "code": "GE_0001",
    "message": "Malformed json"
  },
  "success": false
}
{
  "error": {
    "code": "FS_0003",
    "message": "Invalid data passed",
    "validations": [
      {
        "validation_code": "WRONG_DATA_TYPE",
        "meta_data": {
          "fields": [
            "image_url"
          ]
        }
      }
    ]
  },
  "success": false
}

Error codes

 
Error Code
Reason

FS_0001

Duplicate Reference Id

FS_0002

Reference Id Missing

FS_0004

Data missing

FS_0005

Tag Missing

FS_0006

Feed Line Unit not found

FS_0007

Image urls not valid

GE_0001

Malformed JSON/Invalid UUID passed

GE_0002

Parameter missing

What we send

 

You will be required to configure a callback_url, where we will POST the results of your request once it is completed.

POST https://<some_custom_callback_url>

We send the response as a JSON body, which looks like this:

{
    "feed_line_units": [{
   	 "reference_id": "001",
   	 "flu_id": "33abc3fe-9fbc-4d7c-b951-a1d1bfb6f840",
   	 "status": "COMPLETED",
   	 "tag": "cat_or_dog",
   	 "result": {
       "category" : "cat"
    }]
}

The result object is a JSON which can contain one or more key-value pairs, depending on your requirements. Check the examples to understand how it can be used in various scenarios.

In case the images shared in the Feedline API are invalid or unavailable, we will retry multiple times before responding asynchronously to the Callback API with "status": "FAILED"

{
  "feed_line_units": [
    {
      "reference_id": "001",
      "flu_id": "33abc3fe-9fbc-4d7c-b951-a1d1bfb6f840",
      "status": "FAILED",
      "tag": "cat_or_dog",
      "error": {
        "code": "FS_0003",
        "message": "Invalid data passed",
        "meta_data": {
          "failures": [
            {
              "field": "product_image_url",
              "type": "INVALID_IMAGE_LINK"
            },
            {
              "field": "review_image_url",
              "type": "INVALID_IMAGE_LINK"
            }
          ]
        }
      }
    }
  ]
}

Parameters

content-type : application/json

reference_id

reference_id is a unique identifier for a request. We'll fail a request if you've sent another request with the same reference_id previously. This helps us ensure that we don't charge you for work which we've already done for you.

flu_id

This is the unique ID that we generate for every request

status

PENDING : The data is currently being processed
COMPLETED : All the data has been processed and is ready for consumption by client
FAILED : Data validation or file download failed

As of today, you will not receive a response which has a `FAILED' status

tag

Each request should have a tag which tells us what operation needs to be performed on that request. Don't worry, We'll share this tag with you during the integration process.

Authentication

For authentication of the callbacks, we can send a x-playment-key header with each callback. You will need to share the key with us via a secure channel. If you receive requests without the set header, then it is not from Playment's side.

Error codes

 

On a callback request, you should respond with 200 HttpStatusCode to be considered as a successful request. Any non-200 HttpStatusCode will be considered as unsuccessful. In case of following non-200 HttpStatusCodes, we retry upto 3 times in an interval of 30 seconds:

Error Code
Description

408

Request Timeout

500

Internal Server Error

501

Not Implemented

502

Bad Gateway

503

Service Unavailable

504

Gateway Timeout

505

HTTP Version Not Supported

511

Network Authentication Required

Security

 
  • Authentication: The secret ‘x-client-key’ for each of our clients ensures that only you are able to access your projects
  • To ensure network security, you can whitelist our IP addresses so that you accept callback requests originating only from our servers.
  • Image urls on the app can be encrypted and signed so that they are accessible only from the client's device.
  • HMAC encryption support

Bounding Boxes

 
{  
   "reference_id":"001",
   "data":{
     "image_url":"https://dummyimage.com/600x400/000/fff.jpg&text=Dummy+Image+1"
   },
   "tag":"draw_landmark"
}
{
    "feed_line_units": [{
   	 "reference_id": "001",
   	 "flu_id": "33abc3fe-9fbc-4d7c-b951-a1d1bfb6f840",
   	 "status": "COMPLETED",
   	 "tag": "draw_bounding_boxes",
   	 "result": [
       {
         "label": "television",
         "coordinates": {"xmin":0.38, "ymin":0.19,"xmax":0.57, "ymax":0.44}
       },
       {
         "label": "plant",
         "coordinates": {"xmin":0.38, "ymin":0.19,"xmax":0.57, "ymax":0.44}
       }
       ...
     ]
    ]
}

Cuboids

Perceive 3D depth from 2D images

 
{  
   "reference_id":"002",
   "data":{
     "image_url":"https://dummyimage.com/600x400/000/fff.jpg&text=Dummy+Image+1"
   },
   "tag":"draw_cuboids"
}
{
	"feed_line_units": [{
		"reference_id": "002",
		"flu_id": "3bcbc3fe-9fbc-4d7c-b951-a1d1bfb6f840",
		"status": "COMPLETED",
		"tag": "draw_cuboids",
		"result": {
			"cuboids": [{
				"points": {
					"p1": {"x": 0.17,"y": 0.58},
					"p2": {"x": 0.26,"y": 0.58},
					"p3": {"x": 0.26,"y": 0.49},
					"p4": {"x": 0.17,"y": 0.49},
					"p5": {"x": 0.35,"y": 0.36},
					"p6": {"x": 0.35,"y": 0.52},
					"p7": {"x": 0.24,"y": 0.51},
          "p8": {"x": 0.25,"y": 0.57}
				},
				"front": {
					"coordinates": ["p1","p2","p3","p4"] //clockwise
				},
				"side": {
					"coordinates": ["p2","p3","p5","p6"]
				},
				"back": {
					"coordinates": ["p7","p8","p5","p6"]
				},
				"label": "Car - Sedan",
        "faces_visible": ["right","back"]
			}...
			]
		}
	}]
}

Landmark Annotation

 
Landmarks on Human Face

Landmarks on Human Face

{  
   "reference_id":"001",
   "data":{
     "image_url":"https://dummyimage.com/600x400/000/fff.jpg&text=Dummy+Image+1"
   },
   "tag":"draw_landmarks"
}
{
  "person1": [
    {
      "_id": "f3c05cf9-4c2f-45c9-9a96-45c88a4ef410",
      "points": {
        "p1": {
          "x": 620,
          "y": 510,
          "label": "left_eye",
          "visibility": 2
        },
        "p2": {
          "x": 710,
          "y": 520,
          "label": "left_shoulder",
          "visibility": 2
        },
        "p3": {
          "x": 694,
          "y": 512,
          "label": "right_shoulder",
          "visibility": 1
        },
      }
    }
  ]
}

Polygons

 
{  
   "reference_id":"001",
   "data":{
     "image_url":"https://dummyimage.com/600x400/000/fff.jpg&text=Dummy+Image+1"
   },
   "tag":"draw_polygons"
}
{
	"feed_line_units": [{
		"reference_id": "001",
		"flu_id": "3bcbc3fe-9fbc-4d7c-b951-a1d1bfb6f840",
		"status": "COMPLETED",
		"tag": "draw_polygons",
		"result": {
			"polygons": [{
				"points": {
					"p1": {"x": 0.17,"y": 0.58},
					"p2": {"x": 0.26,"y": 0.63},
					"p3": {"x": 0.27,"y": 0.63},
					"p4": {"x": 0.29,"y": 0.59},
					"p5": {"x": 0.25,"y": 0.46},
					"p6": {"x": 0.22,"y": 0.42}...
				},
				"edges": {
					"e1": ["p1","p2"],
					"e2": ["p2","p3"],
					"e3": ["p3","p4"],
					"e4": ["p4","p5"],
					"e5": ["p5","p6"],
					"e6": ["p6","p7"],
					"e7": ["p8","p9"]...
				},
				"label": "Sofa"
			}...
                 ]
		}
	}]
}

Semantic Segmentation

 
Semantically Segmented Urban Scene

Semantically Segmented Urban Scene

{  
   "reference_id":"001",
   "data":{
     "image_url":"https://dummyimage.com/600x400/000/fff.jpg&text=Dummy+Image+1"
   },
   "tag":"semantic_instance_segmentation"
}
{
  "feed_line_units": [
    {
      "reference_id": "001",
      "flu_id": "3bcbc3fe-9fbc-4d7c-b951-a1d1bfb6f840",
      "status": "COMPLETED",
      "tag": "semantic_instance_segmentation",
      "image_url": "https://luigi.playment.io/001.jpg",
      "result": {
        "grayscale_mask": "https://luigi.playment.io/001_grayscale.png",
        "grayscale_label_map": {
          "car" : "1",
          "pedestrian" : "2"
        },
        "grayscale_instance_map": "https://luigi.playment.io/001_instance.png",
        "rgb_mask": "https://luigi.playment.io/001_rgb.png",
        "rgb_label_map": {
          "car" : "#001ADE",
          "pedestrian" : "#BDF032"
        },
        "segmentation": {
          "points": {
            "p1": {"x": 0.17,"y": 0.58},
            "p2": {"x": 0.26,"y": 0.63},
            "p3": {"x": 0.27,"y": 0.63},
            "p4": {"x": 0.29,"y": 0.59},
            "p5": {"x": 0.25,"y": 0.46},
            "p6": {"x": 0.22,"y": 0.42
            }
          },
          "segments": [
            {
              "instance_id": "1",
              "label": "Car",
              "exterior": ["p1","p2","p3","p4", "p5"],
              "interior": [
                []
              ]
            }
          ]
        }
      }
    }
  ]
}