Actions140
- Application Load Balancer Actions
- Contract Actions
- Datacenter Actions
- Firewall Rule Actions
- Image Actions
- IP Block Actions
- Kubernetes Cluster Actions
- LAN Actions
- Load Balancer Actions
- Location Actions
- NAT Gateway Actions
- Network Load Balancer Actions
- NIC Actions
- Node Pool Actions
- Private Cross-Connect Actions
- Request Actions
- Security Group Actions
- Server Actions
- Snapshot Actions
- Target Group Actions
- Volume Actions
Datacenter → Get Many
AI-generatedSummary
Retrieves a list of data centers from IONOS Cloud with optional pagination and advanced request settings.
Inputs
- limit — Maximum number of results to return per page (only used when returnAll is false). Default: 50. Range: 1–100.
- returnAll — When true, ignores limit and returns all data centers by automatically paging through the API. Default: false.
- includeRequestStatus — Include the request tracking ID and status URL returned by the IONOS Cloud API for asynchronous operations. Default: false.
- includeResponseHeaders — When true, wraps the response in an object containing the response body under the "body" key, plus "headers" and "statusCode". When false (default), returns only the body.
- requestOptions — Container for low‑level HTTP options (batching, SSL, proxy, timeout). Default: empty object.
- allowUnauthorizedCerts — Allow insecure SSL connections (ignore certificate validation). Default: false.
- proxy — HTTP proxy URL, optionally with credentials (e.g. http://user:pass@host:port). Default: empty (no proxy).
- timeout — Request timeout in milliseconds. Default: 10000 (10 s). Minimum: 1.
Output shape
Array of datacenter objects; if includeResponseHeaders is true, output is an object { body: [...], headers: <response‑headers>, statusCode:
Each datacenter object follows the IONOS Cloud API representation (id, name, description, location, etc.).
Examples
Example 1: Fetch first 20 data centers
{ limit: 20, returnAll: false }
Example 2: Fetch all data centers with full response debugging
{ returnAll: true, includeResponseHeaders: true, includeRequestStatus: true }