v1 · 7 endpoints · live

Image editing
API for developers

Seven AI image processing endpoints behind one API key — background removal, upscaling, watermark and text removal, restoration, colorization, and text-to-image. Plain REST, a JSON response, and nothing stored after the call returns.

  • 7 endpoints, 1 key
  • REST over HTTPS
  • No watermark
  • Nothing stored
bash — remove-background
$ curl -X POST app.imggen.ai/v1/remove-background \
   -H "Authorization: Bearer sk_live_..." \
   -F image=@photo.jpg
→ 200 OK · 128 ms · X-Credit-Remaining: 385
{
  "success": true,
  "image": "iVBORw0KGgoAAAANSUhEUg..."
}

01 — Overview

What is the ImgGen AI image editing API?

The ImgGen AI image editing API is a REST service that performs AI image processing on demand. You POST an image — or a text prompt — to an endpoint over HTTPS, and the processed result comes back base64-encoded in the JSON response. There is no model to host and no GPU to provision.

Every endpoint shares the same base URL, the same API key, and the same response shape, so adding a second capability to your workflow is a change of path rather than a new integration. If you want to try the models before writing any code, the same models power the free ImgGen AI tools in the browser.

02 — Quickstart

How do I use the image editing API?

Generate an API key, then send a multipart request with your image. This example removes a background; every other editing endpoint follows the same pattern with a different path. Image generation is the one exception — it takes a JSON body with your prompt, sample count and aspect ratio instead of a file.

curl --request POST \
  --url 'https://app.imggen.ai/v1/remove-background' \
  --header 'Authorization: Bearer sk_live_YOUR_API_KEY' \
  --form image=@/path/to/photo.jpg
03 — Endpoints

The seven endpoints

Each has its own reference page with parameters, code samples in three languages, and its exact credit cost.

POST /v1/remove-background

Background Removal API

Remove image backgrounds programmatically with a single POST request. One API key, transparent PNG output, and a stateless service that never stores the images you send.

1credit
POST /v1/upscale-image

Image Upscaling API

Increase image resolution 2x or 4x from your own backend. Optional face enhancement and sharpening, JPEG or PNG output, and pricing that scales with the factor you ask for.

2–4credits
POST /v1/remove-watermark

Watermark Removal API

Detect and erase watermarks from images in a single request. Generative inpainting reconstructs the pixels behind the mark, and this is the one endpoint that also accepts a batch of images.

2credits
POST /v1/remove-text

Text Removal API

Erase captions, overlays, timestamps and burned-in labels from images programmatically. Detection is automatic — and if there is no text in the image, you are not charged.

2credits
POST /v1/image-restoration

Photo Restoration API

Repair old, damaged and faded photographs from your own backend. Optionally colorize and increase resolution in the same request instead of chaining three calls.

2credits
POST /v1/colorize-photo

Photo Colorization API

Turn black-and-white photographs into naturally coloured images with one request. Optional tear repair in the same call, and no manual colour picking anywhere in the process.

2credits
POST /v1/generate-image

AI Image Generation API

Generate images from a text prompt with a single JSON request. Up to four samples per call, three models to trade speed against quality, and full commercial rights on the output.

3+credits
04 — Cost

How much does the image editing API cost?

Usage is credit-based rather than a flat per-call fee, so a heavy month and a quiet month cost the same per image. Credits are shared across every endpoint and the web editor — one balance, not a separate quota per tool. A call that fails is refunded automatically, and every successful response returns your remaining balance on the X-Credit-Remaining header.

Credit cost per endpoint
EndpointPathCredits / call
Background Removal/v1/remove-background1
Image Upscaling/v1/upscale-image2–4
Watermark Removal/v1/remove-watermark2
Text Removal/v1/remove-text2
Photo Restoration/v1/image-restoration2
Photo Colorization/v1/colorize-photo2
Image Generation/v1/generate-image3+
ImgGen AI plans and API access
PlanPriceCreditsAPINotes
Free$050 one-time free creditsNo API accessNo credit card required
Starter$9.99 / month400 credits / monthAPI access includedUnused credits roll over
Pro$29.99 / month1,400 credits / monthAPI access + priority supportUnused credits roll over
EnterpriseCustomCustom volumeDedicated infrastructuresupport@imggen.ai

Credit costs and limits last verified 2026-08-27. Full details on the pricing page.

05 — Mechanics

How the API works

Deliberately boring: one request, one response, no orchestration on your side.

ImgGen API request lifecycleYour application sends a multipart POST to the ImgGen API. The upload is written to a temporary object, passed to the AI model, and the result is returned base64-encoded in the same response. The temporary object is deleted once the response is sent. The whole exchange is synchronous, within a 60 second ceiling.YOUR APPany HTTP clientPOST /v1/…multipart · imageIMGGEN APIauth · charge creditsTEMP OBJECTdeleted after sendAI MODELprocesses image200 OK · JSON · base64synchronous · 60s ceiling
One round trip. There is no job to poll and no webhook to register — the processed image is in the body of the response that answers your request.

Synchronous, not queued

The processed image is in the body of the same response. No job ID to poll, no webhook endpoint to stand up, no queue to reconcile. Requests are subject to a 60-second ceiling.

Multipart in, base64 out

Send your input image as a multipart form — JPEG (JPG), PNG and WebP, up to 25 MB. The result comes back base64-encoded in the JSON body: decode it and write it wherever you store assets.

Charged on success only

Credits are deducted atomically and refunded automatically if processing fails, so you are only billed for images that actually come back. Text removal even returns 422 free of charge when there is no text to remove.

Keys you can rotate

Keys are shown once and stored only as a hash. Revocation propagates in about a minute, so a leaked key is a one-minute problem rather than an incident.

06 — Data handling

Does the API store or train on my images?

No. The API is stateless. Unlike the web editor, which saves your projects so you can come back to them, an API call creates no project, no task record, and no stored file. Your upload is written to a temporary object, processed, and deleted as soon as the response is returned. The only thing retained is a usage log recording that a call happened and how many credits it cost.

Your images are never used to train models. That matters if you are processing customer photos you are contractually not allowed to retain — the architecture, not just the policy, is what keeps them out of our storage.

What the API keeps and what it discardsYour upload, the processing step and the returned result all live inside an ephemeral boundary and are deleted once the response is sent. No project, task record or stored file is created. The only thing written to storage is a usage log row recording that a call happened and how many credits it cost.EPHEMERAL — DELETED WHEN THE RESPONSE IS SENTUPLOADyour imagePROCESSmodel runsRESULTbase64 out✗ no project✗ no task record✗ no stored filePERSISTEDUSAGE LOGone row · call + credit costNever used to train models.
The architecture, not just the policy — an API call writes no project, task or file row at all.
07 — Errors

Error responses

Failures return a JSON envelope of the shape { "error": { "message", "code" } }, with the HTTP status matching the code.

API error codes
StatusCodeMeaning
401UNAUTHORIZEDThe API key is missing, malformed, or has been revoked.
402INSUFFICIENT_CREDITSYour account does not have enough credits for this call.
403FORBIDDENYour plan does not grant access to this tool.
404NOT_FOUNDThe endpoint path does not exist.
409CONFLICTThe request conflicts with the current state of the resource.
422VALIDATION_ERRORThe request was rejected — a bad file type, a missing field, or nothing to process. No credits are charged.
08 — In production

Who uses the ImgGen API?

Where an image processing API earns its place in a product.

E-commerce and marketplaces

Normalize supplier and seller imagery on upload — cut out backgrounds, strip overlaid text, and upscale small legacy shots so every listing looks like it came from the same studio.

Print-on-demand and product mockups

Isolate artwork, raise resolution to print standards, and composite onto templates without a designer touching each order.

Design and editor SaaS

Ship one-click editing features inside your own product without hosting GPUs, fine-tuning models, or maintaining an inference stack.

Archives, genealogy and digitization

Repair, colorize and enlarge scanned photographs in an automated pipeline instead of retouching every frame by hand.

Content and publishing platforms

Generate original imagery from a prompt and clean up contributor uploads as part of your existing editorial workflow.

Agencies and internal tooling

Automate the repetitive image work that sits between a client brief and a finished asset, driven from the tools your team already uses.

FAQ

Image editing API FAQ

Yes. The ImgGen AI image editing API exposes seven REST endpoints — background removal, image upscaling, watermark removal, text removal, photo restoration, colorization, and text-to-image generation — all under https://app.imggen.ai and all reachable with a single API key.

Get started

Ship your first call in five minutes

Create a key, copy the cURL example, and you have background removal running. One key covers all seven endpoints, on every plan that includes API access.

Get your API key