minimax_files_retrieve

Technical Specifications of minimax-files-retrieve

What is minimax-files-retrieve?

minimax-files-retrieve is CometAPI’s platform identifier for MiniMax’s file retrieval capability. It is not a text-generation model; instead, it is a utility-style API operation used to fetch information about a previously uploaded or generated file on the MiniMax platform. The official MiniMax documentation describes this as part of its File Management API, which includes endpoints for upload, listing, retrieval, content retrieval, and deletion.

In practice, this endpoint is used after another MiniMax workflow has produced or referenced a file. For example, MiniMax documents note that video generation and certain asynchronous tasks return a file_id, and that this file_id can then be used with the retrieve endpoint to obtain file metadata and a downloadable URL.

Because of that role, minimax-files-retrieve is best understood as an integration component in a larger multimodal pipeline: upload or generate a file elsewhere, then call this API to confirm the file record and obtain download access. The MiniMax docs also indicate that returned download URLs may be time-limited in some generation workflows, so retrieval is often part of a verification-and-download step rather than a one-time static lookup.

Main features of minimax-files-retrieve

• File metadata retrieval: Returns core file details such as file_id, filename, byte size, creation timestamp, and file purpose, making it useful for auditing and downstream automation.
• Download URL access: Provides a download_url field so applications can fetch generated or stored assets after processing is complete.
• Pipeline compatibility: Works with other MiniMax services, especially file-producing workflows like video generation and asynchronous media tasks that output a file_id.
• Simple request design: Uses a straightforward authenticated GET request with a required file_id, which makes it easy to integrate into backend jobs, dashboards, and post-processing scripts.
• Part of broader file management: Sits inside a full file-management suite that also includes upload, list, retrieve content, and delete operations, enabling full lifecycle handling rather than isolated retrieval only.
• Useful for verification workflows: The returned status structure and file object let developers confirm that a file exists and is associated with the expected purpose before attempting download or further processing.

How to access and integrate minimax-files-retrieve

Step 1: Sign Up for API Key

To access the minimax-files-retrieve API, first create an account on CometAPI and generate your API key from the dashboard. After signing in, store the key securely and use it as a Bearer token in your request headers. MiniMax’s official API documentation indicates that its file retrieval endpoint also uses Bearer authentication, so CometAPI integrations should follow the same standard API-key pattern.

Step 2: Send Requests to minimax-files-retrieve API

Use the model ID minimax-files-retrieve with CometAPI’s standard request flow. This model maps to MiniMax’s file retrieval capability, which is designed to fetch file information using a file_id. The upstream MiniMax API specifies a GET /v1/files/retrieve pattern with Bearer authentication and a required file_id query parameter.

curl --request GET \
  --url https://api.cometapi.com/v1/files/retrieve?model=minimax-files-retrieve&file_id=YOUR_FILE_ID \
  --header "Authorization: Bearer YOUR_COMETAPI_KEY"

Step 3: Retrieve and Verify Results

After sending the request, inspect the returned payload for the file object and status information. A successful response should include fields such as file_id, filename, bytes, purpose, and download_url. Use these fields to verify that the correct file was retrieved and that the download link is present and usable for your workflow. In MiniMax’s ecosystem, this step is especially important for generated assets whose download URLs may be time-sensitive.

{
  "file": {
    "file_id": "YOUR_FILE_ID",
    "bytes": 5896337,
    "created_at": 1700469398,
    "filename": "output_file",
    "purpose": "video_generation",
    "download_url": "TEMPORARY_DOWNLOAD_URL"
  },
  "base_resp": {
    "status_code": 0,
    "status_msg": "success"
  }
}