remove.bg
curl -H 'X-Api-Key: $REMOVE_BG_API_KEY' \
-F 'image_file=@/path/to/file.jpg' \
-F 'size=auto' \
-f https://api.remove.bg/v1.0/removebg \
-o no-bg.pngA two-value API migration
For the standard request in remove.bg’s API docs, your multipart form, field names, and response handling can stay put. Change the URL. Change the key. Ship.
https://api.remove.bg/v1.0/removebghttps://api.backgrounderase.com/v2rbg_live_••••••••••••be_live_•••••••••••••image_file · size=auto · image/pngremove.bg says its background removal service is moving after December 1, 2026. Read their shutdown FAQ.
The exact change
The request body below is identical. Only the highlighted service URL and API-key value move to BackgroundErase.
curl -H 'X-Api-Key: $REMOVE_BG_API_KEY' \
-F 'image_file=@/path/to/file.jpg' \
-F 'size=auto' \
-f https://api.remove.bg/v1.0/removebg \
-o no-bg.pngcurl -H 'X-Api-Key: $BACKGROUNDERASE_API_KEY' \
-F 'image_file=@/path/to/file.jpg' \
-F 'size=auto' \
-f https://api.backgrounderase.com/v2 \
-o no-bg.pngReplace endpoint https://api.backgrounderase.com/v2
Replace secret value BACKGROUNDERASE_API_KEY
A calm rollout
Make the small code change, then give it the same staged rollout you would any production dependency.
Review the API referenceStart the Business trial, then generate a key from API access in your account. Keep it in your server-side secret store.
Start Business trialReplace the remove.bg endpoint and the secret value. Keep the X-Api-Key header name, multipart body, file field, and binary response handling.
Use a representative image and your existing request options. A successful cutout returns image bytes with a 200 response.
Open API docsDeploy through staging, compare a small batch of outputs, then switch production traffic and watch status codes and latency.
Standard REST compatibility
BackgroundErase accepts the common multipart fields used in direct remove.bg calls and returns binary image data for the same simple write-to-file flow.
200 OK · image/png✓image_file✓image_url✓image_file_b64✓size✓format✓channels✓crop✓bg_color✓bg_image_url✓bg_image_fileThe two-value swap is for standard direct REST cutout requests. If your integration depends on ZIP output, OAuth, ROI, positioning, generated shadows, or a remove.bg-specific SDK, map those parts before switching production traffic.
BackgroundErase Business
Start with a 7-day trial and 1,000 API calls. Then pay a flat Business subscription plus the images you process.
Business
Migration FAQ
No. HTTP header names are case-insensitive, and BackgroundErase accepts x-api-key. You can leave X-Api-Key exactly as it appears in the remove.bg example and replace only the key value.
Yes. Standard multipart requests can keep image_file or image_url, along with common options such as size, format, channels, crop, and bg_color.
Yes. A standard multipart request returns binary image data, so existing code that writes response bytes to a file can stay in place.
Call BackgroundErase over HTTP rather than through a remove.bg-specific SDK. ZIP output, OAuth, ROI, positioning, and generated-shadow options are not part of the two-value swap; map or remove those before rollout.
Before December 1, 2026
Get a BackgroundErase key, copy the request above, and test your production-shaped call today.
BackgroundErase is not affiliated with remove.bg, Canva, or Leonardo.Ai.