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

Palo Alto Networks Connector API

The Connector API from Palo Alto Networks — 13 operation(s) for connector.

Palo Alto Networks Connector API is one of 741 APIs that Palo Alto Networks publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 22 operations across 13 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against a single base URL, https://api.sase.paloaltonetworks.com.

22 operations 13 paths 18 schemas 2 DELETE11 GET6 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://{firewall}/api/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Palo Alto Networks Connector API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 22

Across 13 paths, the API surfaces 22 operations — 2 DELETE, 11 GET, 6 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Connector 22
GET
/sse/connector/v2.0/api/connectors
List Connectors
list.connectors.v2 6 params → 200400401
POST
/sse/connector/v2.0/api/connectors
Create Connector
create.connector.v2 1 param body → 201400401403409
GET
/sse/connector/v2.0/api/connectors/{oid}
Get Connector
get.connector.v2 2 params → 200400401404
PUT
/sse/connector/v2.0/api/connectors/{oid}
Update Connector
update.connector.v2 2 params body → 200400401403404409
DELETE
/sse/connector/v2.0/api/connectors/{oid}
Delete Connector
delete.connector.v2 2 params → 202400401403404409
GET
/sse/connector/v2.0/api/connectors/filters
List Connector Filters
list.connector.filters.v2 3 params → 200400401
GET
/sse/connector/v2.0/api/connectors/{oid}/quiesce
Get Connector Quiesce State
get.connector.quiesce.v2 2 params → 2004004014044245XX
PUT
/sse/connector/v2.0/api/connectors/{oid}/quiesce
Update Connector Quiesce State
update.connector.quiesce.v2 2 params body → 2044004044245XX
POST
/sse/connector/v2.0/api/connectors/{oid}/scheduled-upgrade
Create Connector Scheduled Upgrade
create.connector.scheduled_upgrade.v2 1 param body → 201400404
GET
/sse/connector/v2.0/api/connectors/{oid}/scheduled-upgrade
Get Connector Scheduled Upgrade
get.connector.scheduled_upgrade.v2 1 param → 200400401404
PUT
/sse/connector/v2.0/api/connectors/{oid}/scheduled-upgrade
Update Connector Scheduled Upgrade
update.connector.scheduled_upgrade.v2 1 param body → 204400404
DELETE
/sse/connector/v2.0/api/connectors/{oid}/scheduled-upgrade
Delete Connector Scheduled Upgrade
delete.connector.scheduled_upgrade.v2 1 param → 202400401403404
GET
/sse/connector/v2.0/api/connectors/{oid}/scheduled-upgrade-status
Get Connector Scheduled Upgrade Status
get.connector.scheduled_upgrade_status.v2 2 params → 2004004014045XX
GET
/sse/connector/v2.0/api/connectors/{oid}/pcaps
List Connector Packet Capture Files
list.connector.packet_captures.v2 1 param → 200400401
POST
/sse/connector/v2.0/api/connectors/{oid}/pcaps
Start Connector Packet Capture
start.connector.packet_capture.v2 1 param body → 200400401
POST
/sse/connector/v2.0/api/connectors/{oid}/pcaps/{id}:stop
Stop Connector Packet Capture
stop.connector.packet_capture.v2 2 params → 200400401
GET
/sse/connector/v2.0/api/connectors/{oid}/pcaps/{id}:download
Download Connector Packet Capture File
download.connector.packet_capture_file.v2 2 params → 200400401
GET
/sse/connector/v2.0/api/connectors/{oid}/tech-support-files
List Connector Tech Support Files
list.connector.tech_support_files.v2 1 param → 200400401
POST
/sse/connector/v2.0/api/connectors/{oid}/tech-support-files
Start Connector Tech Support Generation
generate.connector.tech_support_file.v2 1 param → 200400401
POST
/sse/connector/v2.0/api/connectors/{oid}/tech-support-files/{id}:stop
Stop Connector Tech Support Generation
stop.connector.tech_support_file.v2 2 params → 200400401
GET
/sse/connector/v2.0/api/connectors/{oid}/tech-support-files/{id}:download
Download Connector Tech Support File
download.connector.tech_support_file.v2 2 params → 200400401
GET
/sse/connector/v2.0/api/connector-images
List Connector Image Versions
list.connect_images.v2 → 200400401

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are connector.status (21 properties), connector.upgrade_status (10 properties), connector.list (4 properties), connector-existing (4 properties). Each schema is shown below with its type and property counts.

pagination.total
integer
pagination.limit
integer
diagnostic_file.list
object
1 property
connector.status
object
21 properties
connector-new
object
3 properties 2 required
connector-existing
object
4 properties 3 required
connector.quiesce
object
1 property 1 required
packet_capture.create
object
4 properties 1 required
error_detail
object
Error detail information following Google Cloud API CauseInfo format
3 properties
pagination.offset
integer
filters
array
connector.upgrade_status
object
10 properties
entity_meta
object
2 properties
error_response
object
Error response payload
1 property 1 required
packet_capture
object
3 properties
connector.scheduled_upgrade
object
3 properties 1 required
connector.list
object
4 properties 4 required
error_object
object
Error object following Google Cloud API error format
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

palo-alto-networks-connector-api-openapi.yml Raw ↑

Other APIs Palo Alto Networks publishes across the network.

PAN-OS XML API
PAN-OS OpenConfig API
Panorama API
AutoFocus API (Deprecated)
Prisma SASE Service Status API
Cross-Platform Service Status API
SASE Authentication Service API
Expedition API (Deprecated)
VM-Series Licensing API
Palo Alto Networks 5G Deregistered Trend API
Palo Alto Networks 5G Network Interconnects and Bandwidth API
Palo Alto Networks 5G Registered Trend API
Where this information came from

This is an independent, third-party profile of Palo Alto Networks Connector 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.