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

pfSense Firewall Rules API

Manage firewall rules.

pfSense Firewall Rules API is one of 5 APIs that pfSense publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Firewall Rules. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://{pfSenseHost}/api/v2.

5 operations 2 paths 1 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://pfsense.local/api/v2
Authentication
HTTP Basic, API Key, HTTP Bearer
License
Resource Areas
1

Authentication & Security 3

pfSense Firewall Rules API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as X-API-Key (apiKeyAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic auth with a pfSense local database username and password.
  • apiKeyAuth — API key generated through the webConfigurator or API endpoints. Keys inherit the permissions of the user that issued them.
  • bearerAuth — JWT bearer token obtained from POST /api/v2/auth/jwt. Tokens default to one hour of validity.

Paths & Operations 5

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

Firewall Rules 5

Manage firewall rules.

GET
/firewall/rules
List firewall rules
listFirewallRules 2 params → 200
GET
/firewall/rule
Get a single firewall rule
getFirewallRule 1 param → 200
POST
/firewall/rule
Create a firewall rule
createFirewallRule body → 200
PATCH
/firewall/rule
Update a firewall rule
patchFirewallRule body → 200
DELETE
/firewall/rule
Delete a firewall rule
deleteFirewallRule 1 param → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is FirewallRule (9 properties). Each schema is shown below with its type and property counts.

FirewallRule
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pfsense-firewall-rules-api-openapi.yml Raw ↑

Other APIs pfSense publishes across the network.

pfSense REST API (pfSense-pkg-RESTAPI)
pfSense Authentication API
pfSense Firewall Aliases API
pfSense Firewall Apply API
Where this information came from

This is an independent, third-party profile of pfSense Firewall Rules 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.