How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

NexGen Cloud Firewalls API

A firewall is a set of inbound and outbound rules scoped to an environment. Attach a firewall to one or more virtual machines or Kubernetes clusters to control which network traffic each resource can send and receive. Default rules block all inbound traffic, add explicit allow rules for SSH, HTTP, or any service you need to expose.

NexGen Cloud Firewalls API is one of 65 APIs that NexGen Cloud publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Firewalls. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 7 operations across 5 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://infrahub-api.nexgencloud.com/v1.

7 operations 5 paths 29 schemas 2 DELETE3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://infrahub-api.nexgencloud.com/v1
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

NexGen Cloud Firewalls API declares 2 security schemes for authenticating requests. An API key is passed in the header as api_key (apiKey). An API key is passed in the header as Authorization (accessToken).

  • apiKey — API-key authentication. Pass your API key as the apikey header value (e.g., apikey: YOURAPIKEY, no prefix). [Generate a key in the Hyperstack console](https://…
  • accessToken — Bearer Token

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 2 DELETE, 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Firewalls 7

A firewall is a set of inbound and outbound rules scoped to an environment. Attach a firewall to one or more virtual machines or Kubernetes clusters to control which network traff…

GET
/core/firewalls
List firewalls
List_existing_firewalls 4 params → 200400401403500
POST
/core/firewalls
Create firewall
Create_firewall body → 200400401403404409500
POST
/core/firewalls/{firewall_id}/firewall-rules
Add firewall rule to firewall
Add_rule_to_firewall 1 param body → 200400401403500
DELETE
/core/firewalls/{firewall_id}/firewall-rules/{firewall_rule_id}
Delete firewall rules from firewall
Delete_rule_from_firewall 2 params → 200400401403404409500
GET
/core/firewalls/{id}
Retrieve firewall details
Get_firewall 1 param → 200400401403404500
DELETE
/core/firewalls/{id}
Delete firewall
Delete_existing_firewall 1 param → 200400401403404409500
GET
/core/sg-rules-protocols
List firewall rule protocols
List_firewall_rule_protocols → 200400401500

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are SecurityGroupRuleFields (9 properties), SecurityGroupRuleFields_2 (9 properties), FirewallDetailFields (8 properties), FirewallDetailFields_2 (8 properties). Each schema is shown below with its type and property counts.

FirewallEnvironmentFields
object
3 properties
FirewallDetailResponse
object
3 properties
FirewallResponse
object
3 properties
Firewall_Rule
object
3 properties
FirewallsListResponse
object
6 properties
Create_Firewall_Rule_Payload
object
6 properties 4 required
Firewall_Attachment_Model
object
4 properties
SecurityGroupRuleFields
object
9 properties
Firewall_Attachment_VM_Model
object
6 properties
FirewallDetailFields
object
8 properties
CreateFirewallPayload
object
3 properties 2 required
ResponseModel
object
2 properties
ErrorResponseModel
object
3 properties
Security_Rules_Protocol_Fields
object
3 properties
FirewallFields
object
6 properties
FirewallEnvironmentFields_2
object
3 properties
FirewallDetailResponse_2
object
3 properties
FirewallResponse_2
object
3 properties
Firewall_Rule_2
object
3 properties
FirewallsListResponse_2
object
6 properties
Create_Firewall_Rule_Payload_2
object
6 properties 4 required
Firewall_Attachment_Model_2
object
4 properties
SecurityGroupRuleFields_2
object
9 properties
Firewall_Attachment_VM_Model_2
object
6 properties
FirewallDetailFields_2
object
8 properties
CreateFirewallPayload_2
object
3 properties 2 required
ResponseModel_2
object
2 properties
ErrorResponseModel_2
object
3 properties
FirewallFields_2
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nexgen-cloud-firewalls-api-openapi.yml Raw ↑

Other APIs NexGen Cloud publishes across the network.

NexGen Cloud Access Keys API
NexGen Cloud Alive API
NexGen Cloud API Key API
NexGen Cloud Assigning Member Role API
NexGen Cloud Auth API
NexGen Cloud Auto Topup API
NexGen Cloud Base Models API
NexGen Cloud beta access API
NexGen Cloud Billing API
NexGen Cloud Buckets API
NexGen Cloud Calculate API
NexGen Cloud Callbacks API
Where this information came from

This is an independent, third-party profile of NexGen Cloud Firewalls API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.