Get a data center
Retrieve a single Runpod data center by ID, optionally including current GPU or CPU availability for Pod deployment.
Authorizations
Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.
Path Parameters
Query Parameters
Comma-separated optional expansions. Supported value: GPU_AVAILABILITY, CPU_AVAILABILITY.
Data center catalog availability expansion.
GPU_AVAILABILITY, CPU_AVAILABILITY Response
OK
"US-TX-3"
"US Texas 3"
Continental region containing the data center.
NORTH_AMERICA, SOUTH_AMERICA, EUROPE, ASIA, MIDDLE_EAST, AFRICA, OCEANIA, ANTARCTICA, UNKNOWN "EUROPE"
Whether this data center supports global networking (private cross-datacenter pod-to-pod network).
true
Network volume tiers this DC supports. Empty = none.
Data center network volume storage type.
STANDARD, HIGH_PERFORMANCE Compliance certifications held by this data center
Compliance certifications.
GDPR, ISO_IEC_27001, ISO_14001, PCI_DSS, HITRUST, SOC_1_TYPE_2, SOC_2_TYPE_2, SOC_3_TYPE_2, ITAR, FISMA_HIGH, HIPAA, RENEWABLE Availability of each GPU this data center offers. Present only when requested with include=GPU_AVAILABILITY, and omitted entirely when the data center offers no GPUs.
Availability of each CPU flavor this data center offers. Present only when requested with include=CPU_AVAILABILITY, and omitted entirely when the data center offers no CPU flavors.