Name

Get a file

The detail of a file of your organization.

HTTP method and path

GET/api/v6/storage/objects/{id}

https://developers.hablame.co/api/v6/storage/objects/{id}

What happens when you run it

Read only: it does not change your organization’s data.
The call is not charged.

What it does

Returns one file, with the same shape as in the list.

Availability and prerequisites

Published and available in the production API v6.
Every path starts at https://developers.hablame.co.
You need a Hablame API key to call it.

Create your API key

Authentication and permissions

Send your API key in the Authorization header with the Bearer scheme.

Who can call it: An API key with the storage service enabled.

Limits and operational notes

Usage limit: 10 requests per second.

The six Storage queries (summary, usage, list, detail, retention and pricing) share this per-organization quota: it is not a per-endpoint quota.

Path parameters

Name Type Description and rules

Name	Type	Description and rules
`id`Required	`string`	File identifier, as it comes in the list. Pattern:`^obj_[0-9A-HJKMNP-TV-Z]{26}$`Example:`obj_01JABCDEFGHJKMNPQRSTVWXYZ0`

idRequired

string

File identifier, as it comes in the list.

Pattern:^obj_[0-9A-HJKMNP-TV-Z]{26}$Example:obj_01JABCDEFGHJKMNPQRSTVWXYZ0

Query parameters

This endpoint has no query parameters.

HTTP headers

Name Type Description and rules

Name	Type	Description and rules
`Authorization`Required	`string`	Your API key with the Bearer scheme. Example:`Bearer hk_TU_API_KEY`

AuthorizationRequired

string

Your API key with the Bearer scheme.

Example:Bearer hk_TU_API_KEY

Request body

This endpoint takes no request body.

Successful responses

200

The file.

This response has no body.

Response fields

Name	Type	Description and rules
`success`Always present	`boolean`
`data`Always present	`object`	A file. It never carries the bucket, the internal path or sequential identifiers.
`data.id`Always present	`string`	File identifier. Example:`obj_01JABCDEFGHJKMNPQRSTVWXYZ0`
`data.name`Always present	`string`	Original name, if the service stored it. May come as `null`.
`data.service`Always present	`string`	Service that stored it.
`data.scope`Always present	`string`	File type within the service.
`data.size`Always present	`integer`	Size in bytes.
`data.contentType`Always present	`string`	MIME type.
`data.storedAt`Always present	`string`	When it was stored (ISO-8601, Colombia time, with milliseconds). May come as `null`. Format:`date-time`
`data.expiresAt`Always present	`string`	When it is deleted under the current retention time, or `null` if it does not expire. May come as `null`. Format:`date-time`
`data.status`Always present	`string`	`available`: it can be downloaded. `deleting`: it is being deleted (or already expired); it cannot be downloaded and is billed until it finishes. Allowed values:`available` `deleting`
`data.deletable`Always present	`boolean`	Whether its file type allows deleting it from the portal before it expires.
`meta`Always present	`object`	Response metadata.
`meta.requestId`Always present	`string`	Unique request identifier (16 hexadecimal characters). It matches the `X-Request-Id` header. Quote it when contacting support. Example:`b9b1704baffab211`
`meta.clientIp`Always present	`string`	IP the API saw your request come from. Useful if your API key only accepts certain networks. Example:`203.0.113.45`
`meta.timestamp`Always present	`string`	Date and time the response was built (ISO 8601 with offset). Format:`date-time`Example:`2026-06-04T19:43:59+00:00`
`meta.responseTimeMs`Always present	`number`	Time (ms) the server took to process the request. Example:`4.24`

Error codes

Every error response has the same shape: success set to false and an error object whose code says what happened. They are grouped here by kind, with the codes this endpoint can return.

Shape of an error response

Name	Type	Description and rules
`success`Always present	`boolean`	Fixed value:`false`
`meta`Always present	`object`	Response metadata.
`meta.requestId`Always present	`string`	Unique request identifier (16 hexadecimal characters). It matches the `X-Request-Id` header. Quote it when contacting support. Example:`b9b1704baffab211`
`meta.clientIp`Always present	`string`	IP the API saw your request come from. Useful if your API key only accepts certain networks. Example:`203.0.113.45`
`meta.timestamp`Always present	`string`	Date and time the response was built (ISO 8601 with offset). Format:`date-time`Example:`2026-06-04T19:43:59+00:00`
`meta.responseTimeMs`Always present	`number`	Time (ms) the server took to process the request. Example:`4.24`
`error`Always present	`object`
`error.code`Always present	`string`	Stable UPPER_SNAKE_CASE identifier. Clients branch on this value. Example:`AUTH_REQUIRED`
`error.legacyCode`	`integer`	Legacy v5 numeric code, only when a bridge exists. Omitted for codes born in v6. Example:`40002`
`error.type`Always present	`string`	URL to the error documentation. Format:`uri`Example:`https://developers.hablame.co/docs/v6/errors/auth-required`
`error.message`Always present	`string`	Human readable text, in English. It is for the developer log, not the end user: do not parse it.
`error.details`Always present	`array<object>`	Structured context (validation issues, affected resource). Empty array when there is no extra context.

Validation

This endpoint does not declare responses of this kind.

Authentication

401Invalid or missing credentials.

401AUTH_REQUIRED
No Bearer token was sent, and every call requires one.
Message the API returns: Authentication is required. Send your API key as `Authorization: Bearer <token>`.
401AUTH_INVALID_KEY
The API key is not recognized: wrong format, revoked or expired.
Message the API returns: The provided API key is invalid or has expired. Please verify the value sent in the `Authorization: Bearer` header.

Permissions

403The API key does not have the Storage service (storage), cannot be used from the request network, or the organization is not active.

403AUTH_SERVICE_NOT_ALLOWED
The key is not allowed to use the service behind this endpoint.
Message the API returns: This API key is not authorized to use the requested service.
403AUTH_IP_NOT_ALLOWED
The key only works from certain networks and your IP is not one of them.
Message the API returns: This API key cannot be used from this IP address. The address we saw is in `meta.clientIp`: call from one of the networks allowed for the key, or use a key that allows this one.
403ACCOUNT_NOT_ACTIVE
Your organization is suspended or closed.
Message the API returns: The organization associated with this API key is not active. Please contact support.

Usage limits

429Request limit exceeded.

429RATE_TPS_EXCEEDED
You exceeded your organization quota for this endpoint.
Message the API returns: You have exceeded the allowed request rate for this endpoint. Please wait before retrying.

Resource not found

404The file does not exist for your organization. It is the same answer for a file that never existed, one from another organization, one already deleted or a malformed id.

404STORAGE_OBJECT_NOT_FOUND
The file does not exist for your organization.

Internal errors and availability

503Storage is not responding right now. Retry after Retry-After.

503SERVICE_UNAVAILABLE
Generic 503: a service we depend on is not responding.

Other responses

This endpoint does not declare responses of this kind.

See it in the error catalog

Special considerations

Files require a key with Storage

Files may be call recordings, audio or documents of your organization. Any API key with the Storage service (storage) can see them, and only the owner of your organization creates keys. Without the service, the key gets 403 AUTH_SERVICE_NOT_ALLOWED here and on every other Storage endpoint.

Endpoints