Skip to main content

Introduction

This API reference describes the RESTful, streaming, and realtime APIs you can use to interact with GMI Inference. REST APIs are usable via HTTP in any environment that supports HTTP requests.

Authentication

The GMI API uses API keys for authentication. Create, manage, and learn more about API keys in your organization settings. Important Security Notes:
  • API keys should be provided via HTTP Bearer authentication:
  • Never expose API keys in client-side code
  • Load keys from environment variables or key management services
  • For multi-organization access, specify headers:

List Video Models

GET https://console.gmicloud.ai/api/v1/ie/requestqueue/apikey/models Lists available models by model_id.

Example Request

Response

Show Model Details

GET https://console.gmicloud.ai/api/v1/ie/requestqueue/apikey/models/{model-id} Retrieves details for {model_id}. Use this to get full details of the model’s schema and parameters.

Example Request

Response

Create Requests

POST https://console.gmicloud.ai/api/v1/ie/requestqueue/apikey/requests The service API handles the full request/response cycle. It accepts the job, publishes status information, and publishes a link to the resulting artifact once processing completes. Clients can enqueue jobs and retrieve details and status. At the end of a successful job, the client can find the artifact details in the final status report.

Example Request

All jobs are processed asyncronously. A successful request will be accepted and enqueued. The server will respond with request details.

Response


Observe Requests

GET https://console.gmicloud.ai/api/v1/ie/requestqueue/apikey/requests/$REQUEST_ID Clients should use the Requests API to find out when a job is complete and retrieve artifact details. The status field indicates if the job is dispatched, processing, finished, or other condition.

Example Request

Response

Monitor a Request

This script will poll the job queue and block until the job is complete.

Fetch the completed artifacts

A successful job will create a dict of output artifacts. Follow the links to retrieve result files.

Example Request

Response


File Handling

Some endpoints accept file URLs or Base64 data URIs. Check each model’s discription for details.

Upload API

If you’d rather not host files yourself, GMI provides a two-step upload that returns a stable public URL. Pass that URL to any endpoint that accepts an image, video, or audio input — for example Kling’s image_list / video_list / element_list (frontal_image, refer_images, refer_videos) or Seedance’s reference_images / reference_videos. 1. Request an upload URL
file_type is the file extension. Allowed values: jpeg, jpg, png, mp4, mp3, wav. Response:
2. Upload the file PUT the raw bytes to upload_url, with Content-Type matching the file type (image/png, image/jpeg, video/mp4, audio/mpeg, audio/wav).
3. Reference the file Use public_url wherever a hosted URL is accepted: