ReWords.AI API

Results and refunds

What results A, B and C (4K) are, when each is returned, failure reasons, and how failed ReWords.AI API jobs are refunded.

Every edit runs up to three pipelines and reports each one separately in results:

ResultWhat it isReturned
AThe AI edit of the whole image.On every successful job.
BThe edited text blended back into your original image, leaving everything else untouched.On every successful job.
CA 4K high-resolution version.Not guaranteed. Our system adds it automatically when the image is suitable, and reports why when it is skipped.

Each result has its own status: succeeded (with a url), failed or skipped (with a reason).

Job status

  • queued — waiting for a free slot; queue_position says how many jobs are ahead.
  • processing — running. A job may run for up to 10 minutes after it starts.
  • succeeded — A or B (or both) produced an image. Charged 1 edit.
  • failed — neither A nor B produced an image. Not charged; error.code says why.

Failure reasons

A failed job's error.code is one of:

CodeMeaning
content_blockedThe image failed content review while processing.
ai_generation_failedThe AI model could not produce a usable image. Retrying often works.
timeoutThe job ran longer than 10 minutes.
upstream_failedAn internal service failed. Retrying often works.
invalid_imageThe file passed the upload checks but could not be decoded.

A single result (A, B or C) that is failed or skipped has a reason from the same list, plus aspect_ratio_unsupported for C (wider or taller than 3:1, so the 4K version was skipped).

Some problems are caught when you submit, before a job exists, and come back as an HTTP error instead: text_not_found (422), invalid_image (400) and image_blocked (403). See Errors.

Result files

Results are JPEG files at public links kept for at least 7 days. See Images for formats and sizes.

On this page