MOmoda
media

Upscale Image

Changed on

Deterministic super-resolution, 2x or 4x (metered provider call).

An image with real transparency is routed to the alpha-preserving engine, which renders 4x only: scale=2 on such an image is rejected with 422 and a message naming both ways forward. Everything else accepts either factor.

Transparency is detected by reading the image, and that read has a size ceiling: above ~24 megapixels the alpha channel is left unread and the image takes the ordinary route, which flattens it. Both factors stay available there. Flatten such a source yourself if its transparency matters.

post/media/upscale

Request

  • Base URL
    https://api.moda.app/v1
  • URL
    https://api.moda.app/v1/media/upscale
  • Auth
    HTTP bearer

Headers

Moda-Version'2026-04-12' | '2026-05-01'
Example:2026-05-01

Calendar-dated API version pin. New integrations should pin 2026-05-01 to opt into the newest response shapes. For back-compat the server also accepts requests with no header and resolves them to the current default (today: 2026-04-12); that default advances on each sunset date. Any unsupported value returns 400 unsupported_version.

Request body

imagestring required

file_ id or http(s) URL.

scaleinteger

2 or 4.

idempotency_keystring nullable

A retried call with the same key replays the stored response (replayed:true) instead of paying for a second provider render.

Response

Successful Response

object required

Changes