Skip to main content
The API reference is generated from OpenAPI. Each endpoint page presents the full URL, authentication, request parameters, code samples, and success or error responses in one flow.

Text & embeddings

Chat, completions, and embeddings.

Image generation

Generate, edit, and process images.

Video generation

Create videos and inspect asynchronous jobs.

Audio & music

Speech, transcription, sound effects, and music.

Tools & presentations

Presentation, file, and image utilities.

Choose an API format

Compare compatible and provider-native APIs.

​
Base settings

​
Read an endpoint page

1

Confirm the method and full URL

The endpoint header displays the HTTP method and complete request URL.
2

Fill in request parameters

Headers, path parameters, query parameters, and body fields are separated and marked with types and required status.
3

Choose a code language

The playground generates code from the current values. Replace API keys, model IDs, and resource URLs before use.
4

Review the response

Responses are grouped by status and media type, including binary image, audio, video, and event-stream bodies.
Use the playground for development checks only. Call the API from your server in production, and never expose an API key in browser code, a mobile application, or a public repository.

​
Synchronous and asynchronous APIs

  • Synchronous endpoints return text, JSON, or binary content in the current response.
  • Asynchronous endpoints return id, task_id, or taskId, then require a status endpoint from the same API family.
  • Providers use different task fields and status values. Follow the selected endpoint contract.
Read Async tasks for polling, timeouts, and result downloads.