API Manual
Use unified authentication to access wylon text, image, and video generation. The manual is organized by capability and workflow so you can quickly find the correct endpoint and parameters.
Integration basics
https://api.wylon.cn/v1$WYLON_API_KEY. Never place a key in frontend code or a public repository.Choose an API by capability
The catalog is organized by user goal. Image and video tasks share a path but use different type values and do not share every parameter.
Text generation
Image generation
Video generation
General endpoints
Make your first read-only call
List models first to confirm the service URL, authentication, and target model ID.
curl https://api.wylon.cn/v1/models \
-H "Authorization: Bearer $WYLON_API_KEY"Synchronous and asynchronous calls
The client remains connected and receives the image in the same response. Use this for interactive experiences where the user is waiting.
Create a task, save its id, and query the status. Use this for background image processing and longer video generation.
- Create task
- Save task ID
- Query status
- Read result
- Download or persist
HTTP 200 on task creation means the task was accepted. The query response status determines whether generation succeeded. Result URLs expire, so download or persist them promptly.
Error handling and retries
| Status | Common cause | Recommended action |
|---|---|---|
400 | Invalid field, type, or model parameter | Correct the request using the endpoint and model documentation |
401 | Missing, invalid, or revoked API key | Check the authorization header and key status |
403 | Insufficient model or task access | Check the account, key, and model permissions |
429 | Rate, concurrency, or capacity limit | Reduce request frequency and increase retry intervals gradually |
500, 503 | Internal error or temporary model unavailability | Query the original task first if you already have its ID |
504 | Synchronous generation exceeded its wait time | Confirm the original request state before creating another request |
Repeating a generation POST creates a separate request or task and may incur additional usage.
