Request Formats

Pixelcut endpoints generally support two request styles:

JSON with `image_url`

Use this when your image is already hosted (recommended for server-side pipelines).

curl -sS "https://api.developer.pixelcut.ai/v1/upscale" \
  -H "X-API-Key: $PIXELCUT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"image_url":"https://cdn3.pixelcut.app/product.jpg","scale":2}'

Multipart with file upload

Use this when you want to upload the image bytes directly.

curl -sS "https://api.developer.pixelcut.ai/v1/remove-background" \
  -H "X-API-Key: $PIXELCUT_API_KEY" \
  -H "Accept: application/json" \
  -F "image=@./product.jpg"

`Accept` header: JSON vs image bytes

Some endpoints support:

Accept: application/json → returns { "result_url": "..." }
Accept: image/* → returns the binary image directly

For production pipelines, application/json + downloading result_url is usually easier to retry and to store.

Result URLs and asset handling

Rate Limits Image Requirements

Getting started

Core concepts

Guides by capability

Resources

JSON with `image_url`

Multipart with file upload

`Accept` header: JSON vs image bytes

Result URLs and asset handling

​JSON with image_url

​Multipart with file upload

​Accept header: JSON vs image bytes

Result URLs and asset handling

JSON with `image_url`

Multipart with file upload

`Accept` header: JSON vs image bytes