Skip to main content

Endpoint

Request Body

The input object accepts model-specific parameters. Some models also support:

Using a configured model fallback

Saving or enabling a model fallback does not automatically apply it to prediction requests. Include fallback_selector in every request that should use it, at the top level alongside model and input, not inside input. Use the saved configuration’s slug, not the fallback model’s slug or ID. The configuration must be enabled and belong to the API key’s organization and the requested primary model. The selector accepts 1-50 lowercase letters and digits separated by single hyphens. For example, if you have saved an enabled configuration with the slug quality-recovery for flux-1-1-pro:
Replace quality-recovery with your saved configuration’s slug. Keep model and input set for the primary model; the saved configuration supplies the fallback models and input mappings. If fallback_selector is omitted, only the primary model runs, even when a fallback configuration exists.

Code Examples

Response

Response Fields

Error Responses

What Happens Next

After creating a prediction, the model processes your input asynchronously. Here’s how you can get your results:
  1. Poll: Use Get Prediction to check status
  2. Webhook: Provide a webhook_url and get results delivered automatically when they’re ready
Every model has different input parameters. Use Get Model to grab the request_schema for any model and see exactly what it expects.
Last modified on September 30, 2026