With every release the Prisma Cloud Compute Edition APIs are versioned to indicate the release number to which they correspond. The version-specific APIs are supported for the subsequent two major releases.
With API versioning, as your Console is upgraded to newer versions, you can continue to use older versioned APIs with stability and migrate to newer version APIs at your convenience within the N-2 support lifecycle.
The deployment scripts and Twistcli that you download from Console, uses the APIs associated with the specific version of Console.
Latest API Versions of Prisma Cloud Compute Edition
To view the documentation for the latest versions of the supported Prisma Cloud Compute Edition releases, visit:
The Compute API is versioned as follows:
v1- Always points to the latest API. This represents a larger set of APIs. Only the following v1 endpoints are supported and documented:
- api/v1/certs/ca.pem, get
- api/v1/certs/server-certs.sh, get
- api/v1/cloud/discovery/entities, get
- api/v1/registry/webhook/webhook, delete
- api/v1/registry/webhook/webhook, post
- api/v1/settings/license, post
- api/v1/signup, post
- api/v1/util/prisma-cloud-jenkins-plugin.hpi, get
- api/v1/util/tas-tile, get
vVersion- Points to a version-specific API, where
Versionspecifies the major and minor parts of a release's version string.
As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported. For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product support lifecycle.
Starting with version 30.xx, each maintenance release (like 30.01, 30.02, and so on) may contain new features and improvements. As a result, the URLs for the APIs will be updated to reflect the version.
You can use different .xx versions of the API at the same time for your automation requirements as we’ll continue to support backward compatibility for two major including minor (maintenance) release versions behind the current one (n-2). For example, while on build 30.01, you can continue to use the API paths such as api/v30.00, api/v22.12, and api/v22.06 due to backward compatibility.
Though we recommend you to update scripts to use the current or new API paths, you won't need to worry about making changes to your code immediately when a new major or minor (maintenance) release is announced.
Note: If you have a mixed environment of different version Defenders, then use the version of the API that matches the earliest version.
If you use the /v1 APIs, Palo Alto Networks recommends that you consider revising your scripts to target the versioned API endpoints. If you opt to continue using the v1 API endpoints, please adhere the to following guidelines:
- Review the list of v1 endpoints you are using and make sure the corresponding versioned endpoints are available.
- If you are using an API that is only in the /v1 category and does not have a corresponding versioned API, you must review your implementation and update your scripts to adapt them to ensure that you do not experience a disruption.
- If you are using /v1 endpoints that are unsupported and not versioned, you can submit a feature request. Your request for supporting the endpoint will be considered when planning the product roadmap for future releases.
The API Reference documentation includes the supported endpoints only. From the Prisma Cloud Compute Console you can download a copy of the OpenAPI spec file. This file lists all available endpoints, including unsupported endpoints. Use the supported endpoints for ensuring stability. Because the unsupported endpoints are not documented for use, they are subject to change, deprecation, or removal without notice.
In the OpenAPI spec, supported endpoints are tagged as supported.
For example, the
POST /api/vX/authenticate endpoint is tagged as follows:
Supported Endpoint Categories
Supported endpoints tend to fall in one of the following categories:
- Reporting endpoints
- Deployment and config
Reporting API calls are the ones used to download health or scan data such as vulnerabilities/compliance/runtime.
Access to the underlying data in JSON and CSV formats allows customers to easily access and transform data into business intelligence in the forms that meet their needs.
The output may be human-readable reports or, in other cases, the reporting data may feed automated decisions and processes.
These are mostly under Monitor section in the Compute Console.
Configuration as code is the formal migration of config between environments, backed by a version control system. Customers who want to programmatically store and manage the configuration of infrastructure components, can utilize these to automate these components using the same approaches that they've used for production code and services.
Deployment and Config
Deployment and config endpoints are essential for properly being able to automate the installation of Console, Defenders, as well as any configuration that deals with integrations.
These are useful to those who base their management of environments on automation, using tools such as Ansible, Puppet, Terraform etc to define desired configurations.