Skip to main content
Changes to /v1 only ever add. A field, an error code or a value you don’t know yet can appear in any answer, so read what you need and ignore the rest. An endpoint marked beta can change or go away without the 180 days’ notice a stable one gets; its answers carry "beta": true, and it stays out of the API reference until it is stable.
Sexual edits of a real person's photo are refused, and the photo check is paused

New error code

  • 422 sexualized_real_person: a run or a batch that would sexualise a real person from a photo you uploaded, refused before anything is held, at no charge. That is words that ask to undress them, put them in lingerie or move them in a suggestive way, on the photo or on an image Leap made from it in an earlier run, and a face swap or a recast (leap/face-swap, leap/video-face-swap, leap/swap with what: "person", leap/recast and the motion-control models) that puts them into a sexual picture or clip. param names what was read: the words, usually input.prompt, or the picture or clip. Ordinary outfit changes, try-ons, swimwear at the beach and dance clips still run, and so do runs with no uploaded photo. See sexualized_real_person.

Changed

  • The photo check is paused, and the docs now say so. Since 10 October 2026 no run reads an uploaded photo for faces or ages, none answers 422 photo_blocked, and POST /v1/photo-checks answers every photo as one adult with framing null. The code and the endpoint stay for when the check comes back. See Photos of people.
FLUX 3 Image takes no seed, bigger MCP uploads, a 402 that says where to go, and defaults for six preview recipes

Changed

  • FLUX 3 Image (black-forest-labs/flux-3-image) takes no seed. Its upstream ignores one, so every run with a seed failed after about a minute, unbilled. A seed now gets 400 invalid_parameter on input.seed before anything runs. The model’s revision is now 2026-10-15.
  • 402 top_up_required names the page that turns keys on, app.tryleap.ai/go/api, where the first $5 top-up (no card fee) is a step of its own. The code and the status are unchanged.
  • Over MCP, upload_file takes an image of up to 3 MB as base64. The MCP endpoint read only 100 KB before, so a larger data got a bare 413. A request over 4 MB now gets a JSON-RPC error that says how to send the file instead: a link, or an upload with the API and its file ID.
  • An iPhone HDR photo (a JPEG that carries a second picture, its gain map) now goes to a model as its main picture alone. Ideogram 4.5 Edit refused such photos as provider_error.
  • Six preview recipes give their required words a default in their input schema, which a run that leaves them out gets: greeting on leap/holiday-card@1, headline on leap/front-page@1, title on leap/invitation@1, country and title on leap/stamp-sheet@1, and idea on leap/anime@1 and leap/tattoo@1. The fields stay in required. Before, leaving one out answered 400.
No welcome credit for new workspaces

Changed

  • New workspaces start with no credit. Sign-up no longer grants the welcome credit, so welcome.status in GET /v1/credits reads none for every workspace made from 14 October 2026, with amount_usd 0.000000. Workspaces made before keep what they got, granted or withheld. Add credits before the first run; the first top-up has no fee.
  • In the studio, a new person’s first image is free, once per person and per inbox: any single image from a model or recipe at settings that cost up to $0.25 to make. It never applies to a run started with an API key or over MCP.
  • New field on models: first_image_free is true on a model or preset whose first image, at its defaults, is free for a new person in the studio. It is absent for everything else, so read a missing field as false.
  • Over MCP, a refusal for an empty balance in a workspace that never topped up says the first top-up has no card fee, before where to add credits.
API keys need a workspace that has paid

Changed

  • An API key starts runs only once its workspace has topped up. Before that, POST /v1/generations and POST /v1/batches with a key answer 402 with the new code top_up_required, whatever the balance, and nothing starts. A key runs as soon as a top-up goes through, and stops again if every top-up is refunded or disputed in full. Reads, quotes, uploads and replays of a run a key already started still work. In October, accounts made only to spend welcome credit through keys cost us real money, so this went out at once, without the usual notice.
  • covered on a plan’s options is always false for an API key, since a key needs a workspace that has paid.
  • The limits before a first top-up no longer reach a key, as a key can’t start runs before one. A key no longer gets 409 unpaid_failure_cap, the 429 for a second run billed by length, or the free transcription minutes.

New error code

  • 402 top_up_required: a run or a batch started with an API key in a workspace that has no top-up it kept. Add credits, then send it again. See top_up_required.
Photo checks, plans, the saved photo, and why a run failed

New in beta

  • POST /v1/photo-checks checks a photo you uploaded before you run it. Send { "file": "file_..." } with a key that has generations:write. The answer has faces, adult, framing (full, waist or face), setting (outdoor or indoor), blocked and moderation_reason. A run of the same photo reuses the answer, and checks are free. See Photos of people.
  • POST /v1/plans turns a person’s own words into what to run. Send { "ask": "me as a giant in Paris" } with a key that has generations:read. The answer’s route is run, clarify, free_tool, api, refuse, link, empty or no_match, with up to three options, each a model and the input the words filled, its cost_usd, and whether the welcome credit covers it. Nothing runs and nothing is stored. Agents get the same answer from the MCP tool plan.
  • GET, PUT and DELETE /v1/me/photo?workspace=<slug> read, keep and delete a person’s saved photo in one workspace. It takes the person’s studio session, not an API key: a key belongs to the workspace, which has no person behind it, so a script passes a file ID in each run instead. Keeping a photo needs is_me: true and a photo with exactly one adult face.
  • POST /v1/ask-drafts keeps up to 280 characters typed on tryleap.ai for an hour and answers an ask_... ID, so the words travel through sign-in by ID and never in a URL. It takes no key, and only the site’s own origin can read the answer in a browser. Each address can keep 20 asks every ten minutes.

New endpoint

  • DELETE /v1/files/{id} deletes a file you uploaded and its bytes, and answers { "id": "file_...", "object": "file", "deleted": true }. Runs that used it keep their results. See Delete a file.

New fields

  • A generation has failure_cause when it failed: provider_error, provider_refused, photo_blocked, timeout, outage, input_removed or input_rejected, so your code can branch without reading error.message. It is null on any other run and on failures from before causes were recorded. Treat a value you don’t know as provider_error. See When a run fails.
  • A preset’s generation has slow_at and deadline_at while it runs. From slow_at you can cancel it whatever it has done, and you pay nothing. At deadline_at Leap stops it, and it fails with failure_cause timeout at no cost.
  • A preset’s preview is now a smaller JPEG, about 960 pixels on its long side, at a link that works for 10 minutes. Read the run again for a fresh link.
  • Each model on /v1/models has expected_seconds, how long Leap’s own runs of it took at its defaults. Each effect has photo, what its photo must show (framing and setting), and a video preset that makes a picture first has still, the frame of the clip that picture becomes and whether it shows as the preview. See Models.
  • GET /v1/credits has welcome: status granted with amount_usd, withheld when the sign-up limits held the welcome credit back, or none. See Pricing.

New error codes

  • 409 file_in_use: DELETE /v1/files/{id} while a run that hasn’t finished uses the file, or while someone in the workspace keeps it as their saved photo. See file_in_use.
  • 409 unpaid_failure_cap: a video run in a workspace that has never topped up, once 6 of its video runs have ended without a charge. Images still run, and the first top-up lifts it. Only workspaces created since this shipped meet it, and a workspace that has paid never does. See unpaid_failure_cap.
  • 422 photo_blocked: the photo check refused a photo the run was given, before anything was held. The error has moderation_reason, minor or nudity, and param names the input. See photo_blocked.

Changed

  • Every photo you uploaded is checked before a run that takes it starts, for every model and preset. When the check can’t run, the run answers 503 with Retry-After and nothing starts. A workspace’s runs can check 600 new photos an hour, and one with several photos refused as possible minors in a day can’t check new ones for 24 hours; both answer 429.
  • A workspace the unpaid limit doesn’t cover (one that has paid, or was created before this shipped) stops getting a run’s preview for the rest of the UTC day once 10 of its runs that showed one have failed for their input.
  • Canceling a preset run after its preview still answers 409 conflict, as before, until the run passes its slow_at.
Last modified on October 17, 2026