Prisma AIRS AI Runtime Management APIs Overview
The Prisma AIRS management APIs are designed to give you powerful, automated control over your Prisma AIRS AI Runtime: API intercept. With management APIs, you can manage applications, API keys, security profiles, and custom topics programmatically, instead of through Strata Cloud Manager as before.
This makes it much easier to integrate Prisma AIRS Runtime security with your existing systems and manage security for many AI applications efficiently.
Base URL
All interactions with the Prisma AIRS management APIs begin at the base URL:
https://api.sase.paloaltonetworks.com/aisec
Authentication
This API uses OAuth 2.0 bearer token authentication, and your token must be included in the Authorization header:
Authorization: Bearer YOUR_TOKEN_HERE
For instructions on how to obtain an OAuth 2.0 token, see the Access Tokens section.
API Categories
The Management APIs consist of the following categories:
- API Key Management - Create, manage, and rotate API keys
- AI Security Profiles - Configure and manage AI security profiles
- Custom Topics - Create and manage custom threat detection topics
- Customer Applications - Manage customer application configurations
- Scan Logs - Retrieve and analyze security scan results
- OAuth - Manage OAuth tokens and authentication
- DLP Profiles - Access data loss prevention configurations
- Deployment Profiles - Manage deployment configurations
Prerequisites to Use the Management APIs
The following workflow lists the steps for setting up and using Prisma AIRS Management APIs. For detailed steps, refer to the Strata Cloud Management APIs documentation.
- Configure an Identity: Set up a user role or service account in Strata Cloud Manager to act as the identity for your application or script.
- Create Roles: Use predefined roles or create custom roles and assign them to the identity you configured in the "Configure an Identity" step.
- Obtain a Token: Use your client ID and client secret to retrieve an OAuth 2.0 token.
- Make API Calls: Use the acquired OAuth2.0 token in the
Authorization: Bearer <token>
header for all your API requests.
The next step is to understand the roles that govern what your service account is permitted to do with those tokens.