bgly logobgly

Background Removal API

A background removal API for catalogs, listings, and pipelines

Use the bgly background removal API to send a public image URL, receive a task ID, and poll until the cutout is ready. Standard and HD jobs share the same credit wallet as the website, so you do not maintain a second billing system. Most teams start with a handful of SKUs, then reuse the same request shape for nightly catalog dumps and marketplace refreshes.

This background removal API requires a paid plan or credit purchase. Signup and promotional credits alone do not unlock keys.

Manage API keysRead API docsOpenAPI spec
Mode
Asynchronous
Credits
1 / 2 per image
Formats
PNG, WebP

Background removal API quick start

curl -X POST 'https://bgly.net/api/v1/bg/removals' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"image_url":"https://example.com/photo.jpg","precision":"standard"}'

From API key to cutout URL

The background removal API is asynchronous, so you never hold a request open while the model runs. Create a job, save the ID, and poll until status is succeeded. Timeouts, backoff, and fan-out live in your worker, not in a long-lived HTTP connection to bgly.

  1. 01

    Create an API key

    Sign in, buy a plan or credits, then create a key in Settings → API Keys to authenticate the background removal API. Treat the secret like a password and rotate it if a client is retired.

  2. 02

    Submit a removal

    POST an image_url to /api/v1/bg/removals. Optional subject, precision, and output_format let you bias toward products, portraits, or hair and return PNG or WebP.

  3. 03

    Poll for the result

    GET the task ID every few seconds until status is succeeded, then download output.url. Typical clients wait two to five seconds between polls and stop on a terminal status.

Background removal API capabilities

Built for catalogs, listings, and production pipelines

One versioned background removal API contract. Provider details stay internal; your app only sees tasks, credits, and result URLs. You can change storage or models later without rewriting every client that already polls task IDs.

Async task status

POST creates a job. GET polls until queued, processing, succeeded, or failed. Store the ID in your own table so a crashed worker can resume without creating a duplicate charge.

Shared credit wallet

Standard costs 1 credit. HD (precision high) costs 2. Failed jobs are refunded automatically so a broken source URL does not silently drain the wallet.

Subject and HD modes

Choose auto, product, portrait, or hair, plus standard or high precision. Hair, jewelry, and bottle edges usually look cleaner in HD when the listing sits on a marketplace white background.

Safe retries

Send Idempotency-Key so a network retry returns the original task instead of charging twice. Use a stable key per business event, such as a SKU upload or asset revision.

What teams automate with a background removal API

Use the same background removal API workflow for a single SKU or thousands of listing photos. The create-and-poll loop does not change when volume grows; only your queue width and retry policy do.

Ecommerce catalogs

Clean product shots for Amazon, Shopify, and ads without a studio. Keep originals in your bucket and persist only the cutout URL the listing template needs.

Batch pipelines

Queue many independent jobs with task IDs and idempotent create. Map each source file to one job so a partial outage can resume from the last unfinished ID.

Your own product

Offer a background removal API inside editors, DAM tools, or seller dashboards. Your users only wait for a transparent asset they can place on a new scene.

Background removal API pricing

Pay with the same credits as the website

No separate SKU. Buy Lite, Pro, or a credit pack, then call the background removal API with your key. Usage from the browser tool and from curl draw from one wallet, which keeps finance reports simple.

  • Standard precision: 1 credit per image.
  • HD precision: 2 credits per image.
  • Failed tasks return the reserved credits automatically.
View pricing

Current boundaries

This first public version of the background removal API is URL-in, poll-for-result. Design around these limits for a smoother integration, then add your own queue, alerting, and download-to-storage step.

  • Public HTTP(S) image URLs only — multipart upload is not available yet. Host the file first, or mint a short-lived public object URL.
  • No user webhooks yet. Poll GET /api/v1/bg/removals/:id from a worker you control.
  • The background removal API requires a paid plan or credit purchase. Result URLs may expire — copy the file into your own storage promptly.

Background removal API questions

Practical answers for evaluating and integrating the bgly background removal API into checkout tools, DAM systems, and seller dashboards.

Ready to use a background removal API in your product?

Create an account, buy credits, and make your first background removal API request in minutes. Keep the same key for staging and production as volume grows.

Create an accountRead API docs