Object Detection

Run inference on your object detection models hosted on Roboflow.

There are several ways to run object detection inferences using the Hosted API (Legacy). You can use one of our different SDKs, or send a REST request to our hosted endpoint.

To install dependencies, pip install inference-sdk.

# import the inference-sdk
from inference_sdk import InferenceHTTPClient

CLIENT = InferenceHTTPClient(
    api_url="https://serverless.roboflow.com",
    api_key="API_KEY"
)

result = CLIENT.infer(your_image.jpg, model_id="football-players-detection-3zvbc/12")

API Reference

URL

POST https://serverless.roboflow.com/:projectId/:versionNumber

NameTypeDescription
projectIdstringThe url-safe version of the dataset name. You can find it in the web UI by looking at the URL on the main project view or by clicking the "Get curl command" button in the train results section of your dataset version after training your model.
versionnumberThe version number identifying the version of of your dataset

See how to get your project ID and version number here.

There are two ways you can send an image to the Hosted API (Legacy) via a REST request:

  • Attach a base64 encoded image to the POST request body
  • Send a URL of an image file using the image URL query
    • ex: https://serverless.roboflow.com/:datasetSlug/:versionNumber?image=https://imageurl.com

Query Parameters

NameTypeDescription
imagestringURL of the image to add. Use if your image is hosted elsewhere. (Required when you don't POST a base64 encoded image in the request body.)

Note: don't forget to URL-encode it.
classesstringRestrict the predictions to only those of certain classes. Provide as a comma-separated string.

Example: dog,cat

Default: not present (show all classes)
overlapnumber

The maximum percentage (on a scale of 0-100) that bounding box predictions of the same class are allowed to overlap before being combined into a single box.

Default: 30

This parameter has no effect on RF-DETR models.

confidencenumber

A threshold for the returned predictions on a scale of 0-100. A lower number will return more predictions. A higher number will return fewer high-certainty predictions.

Default: 40

strokenumber

The width (in pixels) of the bounding box displayed around predictions (only has an effect when format is image).

Default: 1

labelsboolean

Whether or not to display text labels on the predictions (only has an effect when format is image).

Default: false

formatstring

Options:

  • json: returns an array of JSON predictions. (See response format tab).
  • image: returns an image with annotated predictions as a binary blob with a Content-Type of image/jpeg.

Default: json

api_keystringYour API key (obtained via your workspace API settings page)

Request Body

TypeDescription
stringA base64 encoded image. (Required when you don't pass an image URL in the query parameters).

The content type should be application/x-www-form-urlencoded with a string body.

Response Format

The hosted API inference endpoint, as well as most of our SDKs, return a JSON object containing an array of predictions. Each prediction has the following properties:

  • x = the horizontal center point of the detected object
  • y = the vertical center point of the detected object
  • width = the width of the bounding box
  • height = the height of the bounding box
  • class = the class label of the detected object
  • confidence = the model's confidence that the detected object has the correct label and position coordinates

Here is an example response object from the REST API:

{
    "predictions": [
        {
            "x": 189.5,
            "y": 100,
            "width": 163,
            "height": 186,
            "class": "helmet",
            "confidence": 0.544
        }
    ],
    "image": {
        "width": 2048,
        "height": 1371
    }
}

The image attribute contains the height and width of the image sent for inference. You may need to use these values for bounding box calculations.

Drawing a Box from the Inference API JSON Output

Frameworks and packages for rendering bounding boxes can differ in positional formats. Given the response JSON object's properties, a bounding box can always be drawn using some combination of the following rules:

  • the center point will always be (x,y)
  • the corner points (x1, y1) and (x2, y2) can be found using:
    • x1 = x - (width/2)
    • y1 = y - (height/2)
    • x2 = x + (width/2)
    • y2 = y + (height/2)

The corner points approach is a common pattern and seen in libraries such as Pillow when building the box object to render bounding boxes within an Image.

Don't forget to iterate through all detections found when working with predictions!

# example box object from the Pillow library
for bounding_box in detections:
    x1 = bounding_box['x'] - bounding_box['width'] / 2
    x2 = bounding_box['x'] + bounding_box['width'] / 2
    y1 = bounding_box['y'] - bounding_box['height'] / 2
    y2 = bounding_box['y'] + bounding_box['height'] / 2
    box = (x1, x2, y1, y2)