Request Format
How to structure API requests
Request Format
Learn how to structure requests to the APIXO API.
Submit Task Endpoint
Replace {model} with the model ID (e.g., nano-banana, flux-2, sora-2).
Request Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer YOUR_API_KEY |
Content-Type | Yes | application/json |
Request Body
Common Parameters
These parameters apply to all models:
| Parameter | Type | Required | Description |
|---|---|---|---|
request_type | string | Yes | How to receive results: async or callback |
callback_url | string | No | Webhook URL for callback mode |
input | object | Yes | Model-specific generation parameters |
request_type
| Value | Description | Use Case |
|---|---|---|
async | Poll for results using the status endpoint | Client-side apps, simple integrations |
callback | Receive results via webhook POST | Production servers, real-time applications |
callback_url
Only required when request_type is callback.
Requirements:
- Must be a publicly accessible HTTPS URL
- Must respond with HTTP 200 within 30 seconds
- Will receive a POST request with the task result
Input Parameters
The input object contains model-specific parameters. Common ones include:
| Parameter | Type | Models | Description |
|---|---|---|---|
mode | string | All | Generation mode (e.g., text-to-image) |
prompt | string | All | Text description of desired output |
image_urls | string[] | Image models | Reference images for editing |
aspect_ratio | string | Most | Output dimensions ratio |
See individual model documentation for complete parameter lists.
Example Requests
Async Mode (Polling)
Callback Mode (Webhooks)
Query Status Endpoint
| Parameter | Type | Required | Description |
|---|---|---|---|
model | path | Yes | Model ID used for generation |
taskId | query | Yes | Task ID from submission response |