Retrieve a file
GET https://api.inoneapi.com/v1/files/{file_id}
Retrieve a file's metadata to inspect upload status, detected type, and original size. This does not return bytes, download links, or signed URLs, and does not check whether the COS object still exists.
Send Authorization: Bearer $INONEAPI_API_KEY; no request body is needed. Access is restricted to the uploading key, including within the same user or project. These operations incur no model inference charges and require no positive balance, but key rate/concurrency limits and project status still apply.
Request parameters
| Parameter | Location | Type | Description |
|---|---|---|---|
file_id | path | string | Required, the complete upload ID: file_ioa_ followed by 32 lowercase hexadecimal characters. Not a Playground or provider ID. |
Request examples
Run the JavaScript examples on Node.js 20+ servers with INONEAPI_API_KEY set.
curl https://api.inoneapi.com/v1/files/file_ioa_0123456789abcdef0123456789abcdef \
-H "Authorization: Bearer $INONEAPI_API_KEY"Response
{
"id": "file_ioa_0123456789abcdef0123456789abcdef",
"object": "file",
"filename": "sample.pdf",
"mime_type": "application/pdf",
"media_type": "document",
"bytes": 1024,
"status": "ready",
"created_at": 1789430400,
"purpose": "user_data"
}HTTP 200 returns the file object. id identifies the file; object is file; filename is the original name; mime_type is detected MIME; media_type is image/video/audio/document; bytes is the original byte count; created_at is Unix seconds; purpose is user_data. status can be uploading or ready; only ready files can be referenced in model requests.
Errors and boundaries
An invalid, missing, or foreign ID returns 404 FILE_NOT_FOUND. Metadata failures return 503 FILE_STORAGE_UNAVAILABLE. Authentication, key status, and rate-limit rules still apply.
Retrieving an uploading record returns HTTP 200 metadata, not 409; referencing it in a model request fails. Interrupted uploads are not guaranteed to recover automatically; avoid endless polling. Public files use an asynchronous one-day COS lifecycle without an expires_at field. An old record may remain ready after deletion. Upload again when content is gone; retrieving metadata does not renew retention.