Image and video API integration

The API base URL is https://api711.my/v1. Send your KEY711 key in an Authorization: Bearer header. Browser login cookies are not a substitute for API-key authentication.

The following example reads metadata only. Set KEY711_API_KEY locally; do not put a usable key into a public page, repository, screenshot or browser-side application.

curl --fail-with-body https://api711.my/v1/models \
  -H "Authorization: Bearer ${KEY711_API_KEY:?Set your KEY711 key locally}"

• GET /v1/models lists model identities permitted for the key.
• GET /v1/video/models returns authorized video capabilities and current quotes.
• POST /v1/images/generations is an image-generation route for models that support that contract; native model formats can differ.
• POST /v1/videos submits a video task. A successful submission is not the completed video.
• GET /v1/videos/{id} reads the task status; GET /v1/videos/{id}/content downloads a completed video with authentication.

Store the returned task ID. Poll its status and request the content only when the task and server copy are ready. Do not repeatedly submit a generation request as a way to check progress.

A network timeout may occur after acceptance. Preserve returned identifiers and investigate before resubmitting. Reference uploads and task creation have different retry and validation conditions.

The complete guide documents model-specific image formats, unified video fields, reference uploads, task polling and authenticated downloads. Its applicable live video-price sections are rendered by the server; a downloaded copy is a snapshot, not a locked future quote.

Keep the same KEY711 base URL when changing models. Follow the selected model's actual contract; do not guess provider-only parameter names, reference support or duration limits.

• Complete API documentation →
• Existing integration clients →
• Create an account →