PicsartRemove Background

Send your Picsart API key as a bearer token on every request.

Authorization: Bearer <PICSART_API_KEY>

One endpoint serves every model: POST to /workflows/v1/models/execute with the model id and its input in the body. The nesting is deliberate — the outer params is the envelope every workflow takes, and the inner one is this model's own input. Those inner names are the same unified ones the SDK takes, so a call translates one-to-one between the two — no per-vendor naming to learn.

curl -X POST 'https://api.picsart.com/workflows/v1/models/execute' \
  -H 'Authorization: Bearer $PICSART_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "params": {
    "model": "picsart-sod-v8-2",
    "params": {
      "imageUrls": [
        "https://cdn.example.com/input.jpg"
      ]
    }
  }
}'

1 parameter, sent inside the inner params object. Identical to the SDK's — one parameter set, whichever transport you use.

The body arrives in the gateway's status envelope, so the output is at response.result — alongside the task id, its status and the amount charged. Asset models return url plus an items array; text models return text instead.

{
  "status": "success",
  "response": {
    "id": "task_abc123",
    "status": "COMPLETED",
    "result": {
      "url": "https://cdn.picsart.com/…/result",
      "items": [
        {
          "url": "https://cdn.picsart.com/…/result"
        }
      ],
      "model": "picsart-sod-v8-2"
    }
  }
}