LassoCut remove.bg-compatible API: the same requests, a new URL and key
LassoCut's API is compatible with the remove.bg API: the same endpoint path, the same form fields, the same X-Api-Key header and the same JSON error format. Code written for remove.bg keeps working after two changes: the base URL and the key.
What stays the same
- https://api.remove.bg/v1.0/ + https://api.lassocut.com/v1.0/
- Endpoints:
POST /v1.0/removebg,GET /v1.0/accountandPOST /v1.0/improve. - Requests:
multipart/form-data, URL-encoded forms or JSON;image_file,image_urlorimage_file_b64;size,type,format,channels,bg_color,bg_image_url,bg_image_file,crop,crop_margin,scale,position,roi, and the older size names. - Responses: the image bytes, or JSON with
result_b64and the foreground box when you sendAccept: application/json; the headersX-Credits-Charged,X-Type,X-Width,X-HeightandX-Foreground-*. - Errors:
{"errors": [{"code", "title", "detail"}]}with the same codes, such asmissing_sourceorfile_too_large. - Libraries: the Python
removebgpackage and PHP'smtownsend/remove-bgwork by changing their endpoint; the LassoCut CLI takes the remove.bg CLI's flags. The migration guide has the code and the full table, parameter by parameter.
A real example


The photo used for the calls on this page (CC0), and a preview cut out by LassoCut through the API.
How to use it
JSON instead of image bytes
curl --fail-with-body -H "X-Api-Key: $LASSOCUT_API_KEY" \
-H "Accept: application/json" \
-F "image_file=@photo.jpg" \
-F "size=preview" \
-o result.json \
https://api.lassocut.com/v1.0/removebg
Run against the production API on 29 September 2026: HTTP 200, application/json, with data.result_b64, foreground_top, foreground_left, foreground_width and foreground_height.
Your balance, free of charge
curl --fail-with-body -H "X-Api-Key: $LASSOCUT_API_KEY" \
https://api.lassocut.com/v1.0/account
Run against the production API on 29 September 2026: HTTP 200, application/json, in the same shape as before (values replaced by …):
{"data":{"attributes":{"credits":{"total":…,"subscription":…,"payg":…,"enterprise":…},"api":{"free_calls":…,"sizes":"all"}}}}
An error, and what it looks like
curl -H "X-Api-Key: $LASSOCUT_API_KEY" \
-F "size=preview" \
https://api.lassocut.com/v1.0/removebg
Run against the production API on 29 September 2026: HTTP 400, application/json, nothing charged:
{"errors":[{"code":"missing_source","title":"No image given","detail":"Please provide the source image in the image_url, image_file or image_file_b64 parameter."}]}
Walkthroughs with error handling for each language: curl, Python, Node.js, PHP.
What LassoCut adds
- Retries don't pay twice: the same request within 10 minutes, or the same
Idempotency-Keyheader, gets the kept result withX-Credits-Charged: 0. - Rate-limit headers:
X-RateLimit-Limit,-Remainingand-Reset, and a 429 withRetry-After. The limit is 500 megapixel-images per minute per account. Server-Timingshows the time spent in each step of the request.- Browser calls: cross-origin requests with
X-Api-Keyare allowed, for in-browser tools such as plugins. Keep your key out of public web pages.
Honest differences
- Shadows: only
shadow_type=dropis drawn. The car and 3D shadow types are accepted but draw nothing yet, andadd_shadow=trueasks for the car shadow, so it draws nothing today. - Input formats: JPG, PNG and WebP, up to 22 MB and 50 MP. Other formats are refused with
invalid_file_type. - Output: PNG results are capped at 10 MP and WebP at 16,383 px per side; full size goes up to 25 MP, or 50 MP with
size=50MP. semitransparencyis accepted for compatibility.- Pricing is LassoCut's own: credit packs, no subscription, 50 free previews a month (up to 10 a day); see pricing.
LassoCut is an independent product: it follows the public shape of the remove.bg API so that existing code keeps working, and it is not affiliated with remove.bg or Canva.
Try it on your own photo
Drop an image on the home page to see the cut-out, then create an account for 50 free previews a month (up to 10 a day).
See also: migration guide · developers · the remove.bg shutdown and your integration · API reference · Python guide · pricing.