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
NAT Gateway → Get Rule
AI-generatedSummary
Retrieves a specific NAT Gateway rule by its ID. Requires the datacenter ID, NAT Gateway ID, and rule ID. Optional flags let you include response headers or request tracking metadata, and advanced request options can tune batching, proxy, timeout, and SSL verification.
Inputs
- datacenterId (required) — The ID of the datacenter containing the NAT Gateway.
- natGatewayId (required) — The ID of the NAT Gateway.
- ruleId (required) — The ID of the NAT Gateway rule to retrieve.
- includeRequestStatus — Whether to include the request tracking ID and status URL from async operations (generally not applicable for GET). Defaults to false.
- includeResponseHeaders — When enabled, returns an object with
body,headers, andstatusCode; otherwise returns the rule object directly. Defaults to false. - requestOptions — Advanced HTTP request options: batching, proxy, timeout, and SSL settings.
Output shape
If includeResponseHeaders is false: the NAT Gateway rule object as returned by the IONOS Cloud API. If includeResponseHeaders is true: an object { body: <rule>, headers: <...>, statusCode: <number> }. The includeRequestStatus flag does not affect GET responses but may add tracking fields when present.
The requestOptions sub‑fields include batching (batchSize, batchInterval), allowUnauthorizedCerts, proxy, and timeout. They are passed through to the underlying HTTP client.