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
Firewall Rule → Get
AI-generatedSummary
Retrieves a firewall rule from IONOS Cloud using its datacenter, server, NIC, and firewall rule IDs.
Inputs
- Datacenter ID (required) — ID of the datacenter containing the server.
- Server ID (required) — ID of the server containing the NIC.
- NIC ID (required) — ID of the NIC containing the firewall rule.
- Firewall Rule ID (required) — ID of the firewall rule to retrieve.
- Include Request Status — Defaults to false. Option to include a request tracking ID and status URL for asynchronous operations; the description says these come from non-GET responses.
- Include Response Headers — Defaults to false. When enabled, returns the response body under a
bodykey, with HTTP headers and status code alongside it. - Request Options — Optional batching, SSL certificate validation, proxy, and timeout settings.
Output shape
A single firewall rule response, or a response envelope when response headers are included.
The source pack contains no operation implementation beyond source map markers, so the returned fields and request-status behavior cannot be confirmed from source. The UI describes the response envelope as
{ body, headers, statusCode }when Include Response Headers is enabled.