Skip to main content
GET
/
storage
/
v4
/
object_storages
/
{storage_id}
Get S3-compatible storage
curl --request GET \
  --url https://api.gcore.com/storage/v4/object_storages/{storage_id} \
  --header 'Authorization: <api-key>'
{
  "address": "luxembourg-2.storage.example.com",
  "created_at": "2025-08-05T09:17:02Z",
  "full_name": "696-my-storage-prod",
  "id": 1,
  "location_name": "luxembourg-2",
  "name": "my-storage-prod",
  "provisioning_status": "active"
}

Documentation Index

Fetch the complete documentation index at: https://gcore.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

API key for authentication. Make sure to include the word apikey, followed by a single space and then your token. Example: apikey 1234$abcdef

Path Parameters

​
storage_id
integer<int64>
required

Storage ID

Response

S3StorageListItemV4

​
address
string
required

Full hostname/address for accessing the storage endpoint

Example:

"luxembourg-2.storage.example.com"

​
created_at
string<date-time>
required

ISO 8601 timestamp when the storage was created

Example:

"2025-08-05T09:17:02Z"

​
full_name
string
required

Read-only internal full name of the storage, composed as "{client_id}-{name}". Used internally by the backend. Clients should continue to identify the storage by name.

Example:

"696-my-storage-prod"

​
id
integer<int64>
required

Unique identifier for the storage instance

Example:

1

​
location_name
string
required

Geographic location code where the storage is provisioned

Example:

"luxembourg-2"

​
name
string
required

User-defined name for the storage instance, as supplied at creation time.

Example:

"my-storage-prod"

​
provisioning_status
enum<string>
required

Lifecycle status of the storage. Use this to check readiness before operations.

Available options:
creating,
active,
updating,
deleting,
deleted
Example:

"active"