Get file
Read one file’s source metadata and processing state.
/namespaces/{namespace}/collections/{collection}/files/{file}PermissionCluster key, or a scoped key with read (write includes read). Key scopes and actions.
- Use a fil_ ID, or encode a logical path as one URL segment. For simpler exact-path lookup, use the file list’s path parameter.
- This response contains file metadata, not file bytes.
Path parameters
Namespace name or ns_ ID. It must be visible to this key.
Collection name or col_ ID within the namespace. It must be visible to this key.
File ID with the fil_ prefix, or a file path encoded as one URL segment. Encode each / as %2F. Exact path lookup is also available with GET files?path=.
Responses
200Success
The requested resource or result.
application/json
Response headers
The Engine request ID. Retain it when investigating a failed or unexpected request.
The X-Request-Id you sent, echoed when it is a valid ID. Otherwise, the Engine request ID.
Time the resource was created, as an ISO 8601 UTC timestamp.
Processing failure details. Omitted when the file has no error.
Rule that governs retrieval of this file. Present only when the collection enforces access rules.
Immutable file ID with the fil_ prefix. Retain this ID from the add response.
Application data attached to the file, as a JSON object. Values may be any JSON value. A filter can read metadata.<key> only when the collection lists that key in its metadata fields.
Case-sensitive path within the collection, such as /reports/incident.txt. Start with / and omit a trailing /. Maximum 1,024 UTF-8 bytes. Empty, dot, parent, and control-character segments are invalid.
Source metadata. Inline text is never returned. Its bytes field is the UTF-8 length of the submitted text.
Current step of an indexing file. Stages only move forward. Null for every other status.
- engine_queued
- Waiting for an Engine worker.
- checking_source
- Engine checks the source and sends it for processing.
- core_queued
- Waiting in the processing queue of the namespace.
- processing
- Engine reads and processes the content.
- building_index
- Processed. Waiting for an index that can serve the file.
Current processing state. Only ready files contribute new indexed content to retrieval.
- pending
- Waiting for bytes or processing.
- indexing
- Building searchable content.
- ready
- Available for retrieval.
- failed
- Processing failed. Inspect error.
- deleting
- Removal and cleanup are in progress.
Time the resource last changed, as an ISO 8601 UTC timestamp.
Errors
Select an error in the response example to see its JSON body. See error handling for the common error format.
- 400invalid_request
A field, path, parameter, or conditional request rule is invalid.
What to do: Correct the request. Unknown fields are rejected.
- 401unauthenticated
The API key is missing, invalid, or revoked.
What to do: Send an active key in Authorization: Bearer or X-API-Key.
- 403forbidden
The key can see the resource but lacks permission for this operation.
What to do: Use a key with the required action or scope kind.
- 404not_found
The resource is absent, deleted, or outside this key’s scope.
What to do: Check the identifier and the key’s namespace and collection scope.
- 500internal_error
An unexpected server failure prevented this request from completing.
What to do: Retain request_id for investigation. Follow retryable before retrying a write.