Get Region

GET

/topology/v1/engines/{engine}/regions/{id}

curl --request GET \
  --url https://example.com/topology/v1/engines/example/regions/example

Returns a region by its unique identifier, including provider-specific detail.

Parameters

Path Parameters

engine

required

string

The cloud provider, or - to resolve regardless of provider

id

required

string

The unique identifier of the region to retrieve

Responses

200

OK

Media type application/json

Region

A region in the Qibdo Cloud topology — the backing-cluster analog that groups zones. Regions are read-only inventory built by the per-provider sync source; they are never user-created and move only through the location lifecycle verbs. Every field is server-managed.

object

id

The unique identifier of the region

stringOutput only

name

The DNS-label handle of the region (e.g. “us-east-1”), immutable

stringOutput only

display_name

A human-readable label for the region (e.g. “US East (N. Virginia)”)

stringOutput only

status

The usability status of the region

string format: enum Output only

Allowed values: LOCATION_STATUS_UNSPECIFIED LOCATION_STATUS_PENDING_FOR_APPROVAL LOCATION_STATUS_ACTIVE LOCATION_STATUS_DISABLED

engine

The cloud provider that backs the region

string format: enum Output only

Allowed values: ENGINE_UNSPECIFIED ENGINE_QIBDO ENGINE_AWS ENGINE_GCP ENGINE_AZURE

multi_region_id

The multi-region this region belongs to, if any (at most one)

stringOutput only

created

The timestamp when the region was created

string format: date-time Output only

updated

The timestamp when the region was last updated

string format: date-time Output only

qibdo

Qibdo-specific region detail.

object

cluster_id

The backing Kubernetes cluster handle (a region corresponds to a cluster). May be empty.

stringOutput only

Example

{
  "status": "LOCATION_STATUS_UNSPECIFIED",
  "engine": "ENGINE_UNSPECIFIED"
}

default

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object

code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32

message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string

details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object

@type

The type of the serialized message.

string

key

additional properties

any

Example ^generated

{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}