Run a recipe on one file
A recipe by recipe — a ready-made slug, your saved recipe’s id, or a shared recipe’s public slug — or the steps written inline. Same rules as the Workbench: a step in the wrong place, an option a skill doesn’t have or a paid skill on the free plan is refused before anything is charged. Each skill step is charged as it starts and refunded if it fails.
Authorizations
Authorization: Bearer mm_live_…. Mint a key at mediamonster.app/keys; every plan includes the API. A test key, mm_test_…, runs every check a live key does and spends nothing: each run finishes at once with a stand-in file, and says livemode: false. A key does only what its scopes allow.
Headers
Retry this POST safely: the first request with a key runs and its answer is kept for a day; a retry with the same key and the same request gets that answer again, marked Idempotent-Replayed: true, instead of running twice. 1–255 printable characters — a UUID is a good one.
1 - 255Query Parameters
Body
One file, and the steps to run on it: a recipe by name, or the steps themselves. Every step is checked before anything is charged.
Values for the steps' {{names}}, like {"title": "Summer sale"}. A required input with no default has to be sent; a name the steps don't use is refused. describe_recipe, or GET /api/v1/recipes/{ref}, lists them under inputs. In a multipart form, send a JSON string or one field per input, inputs[title].
Save as, applied to the finished file: {"format": "webp", "quality": "85"}. Or a list of up to 5, one file each, all made from the last step's file: [{"format": "png"}, {"format": "webp"}]. In a list, format takes png, jpeg or webp. An entry that changes nothing on the finished file makes no file. The extra files are free.
- object
- object[]
Response
The run finished while the call waited — or, with dry_run, what it would cost.
- Option 1
- Option 2
A recipe run: its steps in order, each with its state, and the finished files under outputs once every step is done.

