API integration · Pro and Enterprise
An afternoon, not a migration.
One endpoint, bearer auth, a file in and a transparent PNG out. Nothing to install and nothing to keep in sync.
POST
200 OK
curl -X POST \
"https://api.qikkstools.com/v1/remove-background" \
-H "Authorization: Bearer $API_KEY" \
-F "image=@product.jpg" \
-o product.png
returns
product.png · alpha
Before you depend on it
The four questions
Answered here rather than discovered in production.
- How long does a call take?
- Seconds, not milliseconds — it is model time. Treat it as an asynchronous step, not something a page render waits on.
- What do I write?
- A POST with your standard HTTP client. There are no SDKs to adopt, which also means there is no SDK to upgrade.
- What happens on failure?
- Keep the original and retry. Never overwrite the source file with the result — the cut is reproducible, the photograph is not.
- What does it cost?
- API access sits on Pro and Enterprise; the plan page states the limits. The browser tools stay free.
One call, one file
The batch endpoint, for when nobody is waiting
A nightly job over yesterday's uploads is the cheapest way to run this, and the only shape with nothing user-facing to break. Same auth, same response, a set instead of a file.
/v1/batch-process
Or do it without code
Start with the reference
Endpoints, authentication, errors and batch limits, all on one page.