> ## Documentation Index > Fetch the complete documentation index at: https://docs.runpod.io/llms.txt > Use this file to discover all available pages before exploring further. # List data centers > Returns available data center locations with region, compliance, supported network volume tiers, and global networking support. Use include=GPU_AVAILABILITY or include=CPU_AVAILABILITY to add per-resource availability arrays to each data center. The regions, networkVolumeTypes, compliance, and globalNetwork query parameters filter the list before it is returned. ## OpenAPI ````yaml get /v2/catalog/datacenters openapi: 3.1.0 info: title: Runpod REST API version: 2.0.0 description: Runpod public REST API — v2 servers: - url: https://api.runpod.io description: Runpod API v2 production server security: - bearerAuth: [] tags: - name: Pods description: GPU and CPU pod lifecycle, configuration, actions, and log streaming. - name: Serverless description: >- Serverless endpoint lifecycle, worker visibility, releases, and worker log streaming. - name: Templates description: Reusable pod and endpoint configuration templates. - name: Network Volumes description: Persistent network storage volumes for workloads. - name: Registries description: Container registry credentials used to pull private images. - name: Catalog description: Available GPU, CPU, and data center catalog metadata. - name: Billing description: Billing history and usage cost records across resource types. paths: /v2/catalog/datacenters: get: tags: - Catalog summary: List data centers description: > Returns available data center locations with region, compliance, supported network volume tiers, and global networking support. Use include=GPU_AVAILABILITY or include=CPU_AVAILABILITY to add per-resource availability arrays to each data center. The regions, networkVolumeTypes, compliance, and globalNetwork query parameters filter the list before it is returned. operationId: listDataCenters parameters: - name: include in: query required: false description: >- Comma-separated optional expansions. Supported value: GPU_AVAILABILITY, CPU_AVAILABILITY. style: form explode: false schema: type: array items: $ref: '#/components/schemas/DataCenterInclude' example: - GPU_AVAILABILITY - name: regions in: query required: false description: >- Comma-separated DataCenterRegion enum values. Values within this filter use OR semantics. Different filter families combine with AND. style: form explode: false schema: type: array items: $ref: '#/components/schemas/DataCenterRegion' example: - EUROPE - ASIA - name: networkVolumeTypes in: query required: false description: >- Comma-separated volume types. Supported values: STANDARD, HIGH_PERFORMANCE. Values within this filter use AND semantics; volumes=STANDARD,HIGH_PERFORMANCE requires both storage types. Different filter families combine with AND. style: form explode: false schema: type: array items: $ref: '#/components/schemas/VolumeType' example: - STANDARD - HIGH_PERFORMANCE - name: compliance in: query required: false description: >- Comma-separated Compliance enum values. Values within this filter use AND semantics; compliance=GDPR,SOC_2_TYPE_2 requires both certifications. Different filter families combine with AND. style: form explode: false schema: type: array items: $ref: '#/components/schemas/Compliance' example: - GDPR - SOC_2_TYPE_2 - name: globalNetwork in: query required: false description: >- Filter by global networking support. true returns only data centers that support global networking; false only those that do not. Different filter families combine with AND. schema: type: boolean example: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/ListDataCentersResponse' examples: dataCenters: summary: Successful response value: dataCenters: - id: US-KS-2 name: US Kansas 2 region: NORTH_AMERICA globalNetwork: true networkVolumeTypes: - STANDARD - HIGH_PERFORMANCE compliance: - SOC_2_TYPE_2 - ISO_IEC_27001 gpuAvailability: - id: NVIDIA GeForce RTX 4090 name: RTX 4090 availability: HIGH cpuAvailability: - id: cpu3c-2-4 name: Compute-Optimized availability: MEDIUM '401': $ref: '#/components/responses/UnauthorizedError' '403': $ref: '#/components/responses/ForbiddenError' '429': $ref: '#/components/responses/TooManyRequestsError' default: description: Error content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: DataCenterInclude: type: string description: Data center catalog availability expansion. enum: - GPU_AVAILABILITY - CPU_AVAILABILITY DataCenterRegion: type: string description: Continental region containing the data center. examples: - EUROPE enum: - NORTH_AMERICA - SOUTH_AMERICA - EUROPE - ASIA - MIDDLE_EAST - AFRICA - OCEANIA - ANTARCTICA - UNKNOWN VolumeType: type: string description: Data center network volume storage type. enum: - STANDARD - HIGH_PERFORMANCE Compliance: type: string description: Compliance certifications. enum: - 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 ListDataCentersResponse: type: object required: - dataCenters properties: dataCenters: type: array items: $ref: '#/components/schemas/DataCenter' ErrorResponse: type: object required: - title - status - detail properties: title: type: string description: Short human-readable summary examples: - Not Found status: type: integer description: HTTP status code examples: - 404 detail: type: string description: Human-readable explanation examples: - pod not found errors: type: array description: Individual request-validation failures. items: type: string examples: - - '$: additional properties ''bogus'' not allowed' DataCenter: type: object required: - id - name - region - networkVolumeTypes - compliance - globalNetwork properties: id: type: string examples: - US-TX-3 name: type: string examples: - US Texas 3 region: $ref: '#/components/schemas/DataCenterRegion' globalNetwork: type: boolean description: >- Whether this data center supports global networking (private cross-datacenter pod-to-pod network). examples: - true networkVolumeTypes: type: array items: $ref: '#/components/schemas/VolumeType' description: Network volume tiers this DC supports. Empty = none. compliance: type: array description: Compliance certifications held by this data center items: $ref: '#/components/schemas/Compliance' examples: - - GDPR - ISO_IEC_27001 - SOC_2_TYPE_2 gpuAvailability: type: array description: >- Per-GPU availability in this data center. Present only when requested with include=GPU_AVAILABILITY. items: $ref: '#/components/schemas/CatalogResourceAvailability' cpuAvailability: type: array description: >- Per-CPU availability in this data center. Present only when requested with include=CPU_AVAILABILITY. items: $ref: '#/components/schemas/CatalogResourceAvailability' CatalogResourceAvailability: type: object required: - id - name - availability properties: id: type: string description: Catalog resource identifier. examples: - NVIDIA GeForce RTX 4090 name: type: string description: Human-readable catalog resource name. examples: - RTX 4090 availability: $ref: '#/components/schemas/AvailabilityLevel' AvailabilityLevel: type: string description: Catalog stock availability level. enum: - NONE - LOW - MEDIUM - HIGH responses: UnauthorizedError: description: >- Authentication failed because the bearer token is missing, malformed, expired, or invalid. content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' examples: missingBearerToken: summary: Missing bearer token value: title: Unauthorized status: 401 detail: missing bearer token ForbiddenError: description: >- The bearer token is valid, but it does not grant access to the requested resource or action. content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' examples: insufficientAccess: summary: Insufficient access value: title: Forbidden status: 403 detail: access denied TooManyRequestsError: description: > The caller exceeded its per-user rate limit. The response identifies the window that was exceeded and how long to wait. The `RateLimit` and `RateLimit-Policy` headers (per the IETF ratelimit-headers draft) also accompany successful responses, so clients can track quota before a 429. headers: Retry-After: description: Seconds to wait before retrying, per the exceeded window. schema: type: integer example: 12 RateLimit: description: > Live per-window state as a structured-field list — one member per window (`minute`, `hour`, `day`) with remaining count `r` and seconds-until-reset `t`. schema: type: string example: '"minute";r=0;t=12, "hour";r=2800;t=1812, "day";r=49500;t=45012' RateLimit-Policy: description: > Static quota policy as a structured-field list — one member per window with quota `q` and window length `w` (seconds). schema: type: string example: '"minute";q=60;w=60, "hour";q=3000;w=3600, "day";q=50000;w=86400' content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' examples: rateLimited: summary: Rate limit exceeded value: title: Too Many Requests status: 429 detail: rate limit exceeded for the minute window securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: Runpod API Key description: > Runpod API key authentication. Generate an API key in the Runpod console and send it in the `Authorization` header as `Bearer `. 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. ````