Run the API Script Used to Retrieve IP Addresses

1. Get the API key.

   You need this key to authenticate to Prisma Access and retrieve the list of IP addresses using the API command.

   1. Go to Prisma Access (Managed by Strata Cloud Manager), and select ConfigurationNGFW and Prisma AccessConfiguration ScopePrisma AccessPrisma Access InfrastructureInfrastructure Settings.
   2. Select Generate New API Key.

      If you have already generated an API key, the current key displays. If you have not yet generated a key or want to replace the existing key to meet audit or compliance check for key rotation, click Generate New API Key for a new key.
2. Create a .txt file and put the API command options in the file.

   Using the API the command to use is a two-step process. First, you create a .txt file, specifying the parameters for the IP addresses to retrieve, and save the file in a folder that is reachable from the location where you run the command. Then, you run the API and specify the name and location of the .txt file you created in the command.

   Specify the following keywords and arguments in the .txt file. The examples in this topic use a filename of option.txt but you can specify any filename, as long as you reference it in the command.

   Argument	Possible Choices (Keywords)	Comments
   serviceType	all remote_network gp_gateway gp_portal swg_proxy rbi	all—Retrieves IP addresses you need to add to an allow list for all service types (Remote Networks, Mobile Users (both gateways and portals), and Clean Pipe, as applicable to your deployment). remote_network—Retrieves IP addresses you need to add to an allow list for remote network deployments. gp_gateway—Retrieves the gateway IP addresses you need to add to an allow list for mobile user deployments. gp_portal —Retrieves the portal IP addresses you need to add to an allow list for mobile user deployments. swg_proxy—Retrieves the egress IP addresses for each deployed Explicit Proxy location and the authentication cache service (ACS). rbi—Retrieves the egress IP addresses you need to add to an allow list for Remote Browser Isolation (RBI) deployments to connect to SaaS Applications.
   addrType	all active service_ip auth_cache_service network_load_balancer	all or active—Retrieves all the IP addresses you need to add to an allow list. This API does not retrieve loopback IP addresses. To retrieve loopback IP addresses, use the legacy API command. service_ip—Retrieves the Service IP Address, which you use as the peer IP address when you set up the IPSec tunnel for the remote network connection. auth_cache_service—Retrieves the IP address for the explicit proxy ACS (applicable to Mobile Users—Explicit Proxy deployments only). network_load_balancer—Retrieves the IP addresses for the network load balancer (deployments with IP Optimization enabled only). If you have implemented IP Optimization, be sure you review the allow listing considerations and how to implement the gp_gateway and network_load_balancer IP addresses in your deployment.
   actionType	pre_allocate	Mobile User deployments only—An actionType of pre_allocate allows you to retrieve IP addresses or subnets for Prisma Access gateways and portals for mobile user deployments. Use this with a serviceType of gp_gateway to retrieve pre-allocated gateway IP addresses and a serviceType of gp_portal to retrieve preallocated gateway IP addresses. Retrieving the preallocated IP addresses lets you add the gateway and portal IP addresses to your organization’s allow lists before you onboard mobile user locations, which in turn gives mobile users access to external SaaS apps immediately after you onboard the locations.
   location	all deployed	all—Retrieves the IP addresses from all locations. For mobile user deployments, this keyword retrieves the IP addresses for both locations you added during onboarding, and locations you did not add. deployed—Retrieves IP addresses in all locations that you added during mobile user onboarding. This keyword is applicable to mobile user deployments only. Prisma Access associates IP addresses for every mobile user location during provisioning, even if you did not select that location during mobile user onboarding. If you specify all, the API command retrieves the IP addresses for all mobile user locations, including ones you did not select for the deployment. If you specify deployed, the API command retrieves only the IP addresses for the locations you selected during onboarding.

   Specify the options in the .txt file in the following format:

     {
      "serviceType": "service-type",   
      "addrType": "address-type",
      "location": "location"
      }

3. Enter the following command to retrieve the IP addresses:

   • To use the newer API that was introduced in Prisma Access 2.1, enter the following command:

       curl -X POST --data @option.txt -H header-api-key:Current-API-Key "https://api.prod.datapath.prismaaccess.com/getPrismaAccessIP/v2"

     As of May 2023, some Cloud managed deployments use https://api.prod6.datapath.prismaaccess.com/getPrismaAccessIP/v2 (note the prod6 in the URL instead of prod).
   • To use the legacy API, enter the following command. This command uses a legacy API endpoint that will be deprecated in May 2022:

       curl -X POST --data @option.txt -k -H header-api-key:Current-API-Key "https://api.gpcloudservice.com/getPrismaAccessIP/v2"

   Where option.txt is the .txt file you created in a previous step and Current-API-Key is the Prisma Access API key.

   For example, given a .txt filename of option.txt and an API key of 12345abcde, use the following API command to retrieve the public IP address for all locations:

     curl -X POST --data @option.txt -H header-api-key:12345abcde "https://api.prod.datapath.prismaaccess.com/getPrismaAccessIP/v2"

   The API command can return a large amount of information. To make the output more readable, if you have Python installed, you can add | python -m json.tool at the end of the cURL command.

   The API command returns the addresses in the following format. The following IPs are example addresses only:

   {
       "status": "success",
       "result": [
           {
               "address_details": [
                   {
                       "address": "169.2.3.4",
                       "serviceType": "gp_gateway",
                       "addressType": "active",
                       "create_time": 1743636318,
                       "allow_listed": true
                   },
                   {
                       "address": "137.4.5.6",
                       "serviceType": "gp_gateway",
                       "addressType": "active",
                       "create_time": 1743636318,
                       "allow_listed": true
                   },
                   {
                       "address": "169.7.8.9",
                       "serviceType": "gp_gateway",
                       "addressType": "active",
                       "create_time": 1750812477,
                       "allow_listed": true
                   },
                   {
                       "address": "134.10.11.12",
                       "serviceType": "gp_gateway",
                       "addressType": "network_load_balancer",
                       "create_time": 1743636321
                   }
               ],
               "zone": "US West",
               "addresses": [
                   "169.2.3.4",
                   "137.4.5.6",
                   "169.7.8.9",
                   "134.10.11.12"
               ],
               "zone_subnet": [
                   "140.1.2.0/18",
                   "168.1.2.0/21",
                   "74.1.2.0/20",
                   "128.1.2.0/17",
                   "169.1.2.0/18",
                   "165.1.0.0/16",
                   "34.1.2.0/19",
                   "134.1.0.0/16",
                   "144.1.0.0/16",
                   "208.1.0.0/16",
                   "130.1.0.0/16",
                   "134.1.2.0/17",
                   "137.83.192.0/18",
                   "165.1.2.0/17",
                   "66.1.2.0/19",
                   "34.1.2.0/23"
               ],
               "addresses_v6": [],
               "address_details_v6": [],
               "zone_subnet_v6": [
                   "2606:f4c0:1111:13d4::/64",
                   "2606:f4c0:2222:13d3::/64"
               ],
               "zone_subnet_v6_details": [
                   {
                       "address": "2606:f4c0:1111:13d4::/64",
                       "addressType": "active",
                       "allow_listed": false
                   },
                   {
                       "address": "2606:f4c0:2222:13d3::/64",
                       "addressType": "network_load_balancer",
                       "allow_listed": false
                   }
               ]
           }

   Where:

   • address_details shows the details of the address for each location.
     • serviceType shows the type of IP address (either remote network (remote_network), Prisma Access gateway (gp_gateway), Prisma Access portal (gp_portal), Clean Pipe (clean_pipe), or Remote Browser Isolation (rbi).
     • addressType specifies the type of address specified with the addrType keyword (either active or pre-allocated if you're preallocating IP addresses for mobile user locations).
     • address shows the IP address you need to add to your allow lists.
       If the API returns multiple IP addresses, Prisma Access summarizes the IP addresses in the addresses field.
   • addresses lists all the IP addresses for the location that you need to add to your allow lists.
   • zone is the Prisma Access location associated with the IP addresses.
   • zone_subnet is the subnet for mobile user gateways and portals. Prisma Access also provides this subnet if you're preallocating IP addresses for mobile user locations.
   • zone_subnet_details provides you with more information about the mobile user gateways and portals. Prisma Access also provides this subnet if you're preallocating IP addresses for mobile user locations.
   • addresses_v6, address_details_v6, and zone_subnet_v6, are the IPv6 addresses equivalent to addresses. address_details, and zone_subnet, respectively.
     Prisma Access provides you with IPv6 subnets instead of IP addresses when you have enabled IPv6; for this reason, you will see zone_subnet_v6 addresses.
   • zone_subnet_v6_details provides you with more information about the IPv6 addresses.
     • address is the IPv6 address that was allocated.
     • addressType (either either active pre-allocated, or network_load_balancer which provides you with the ingress IP addresses (IP Optimization deployments only).
     • allow_listed shows you whether or not these IP addresses have been added to your allow lists and specified as such in the Prisma Access UI.

   If there are any problems with the options in the .txt file, the API returns an error similar to the following:

     {"status": "error","result": "Invalid json format in the request. trace_id: xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx "}

4. Update the allow lists on your on-premises servers or SaaS application policy rules with the IP addresses you retrieved.

API Command Examples

  {
"serviceType": "gp_gateway",
"addrType": "all",
"location": "all"
   }

  {
"serviceType": "gp_gateway",
"addrType": "all",
"location": "deployed"
   }

  {
"serviceType": "gp_gateway",
"addrType": "active",
"location": "deployed"
   }

  {
"serviceType": "remote_network",
"addrType": "all",
"location": "all"
   }

{
"serviceType": "swg_proxy",
"location": "deployed",
"addrType": "auth_cache_service"
}

  {
"serviceType": "rbi",
"location": "all",
"addrType": "all"
  }

Legacy Scripts Used to Retrieve IP and Loopback Addresses

Pre-Allocate IP Addresses for Mobile User Locations

1. Retrieve the Prisma Access API key.
2. Pre-allocate the mobile user egress IP addresses by creating a .txt file and specifying the following options in the .txt file you create.

   Enter the following text in the .txt file:

   • Mobile Users—GlobalProtect Deployments:

       {
        "actionType": "pre_allocate",   
        "serviceType": "gp_gateway",
        "location": ["location"]
        }

   • Mobile Users—Explicit Proxy Deployments:

     {
     "actionType": "pre_allocate",
     "serviceType": "swg_proxy",
     "location": ["location"]}

   Where location is the Prisma Access location where you want to pre-allocate the IP addresses.

   Enter a maximum of 12 locations. Entering more than 12 locations might cause timeout errors when Prisma Access retrieves the pre-allocated IP addresses.
3. Enter this CURL command.
4. Retrieve the IP addresses and subnets you requested, including their validity period, by reopening the .txt file, removing the existing information, and editing it.

   • Mobile Users—GlobalProtect Deployments:
     • To request Prisma Access to retrieve all pre-allocated IP addresses, enter the following text in the .txt file.

         {
          "serviceType": "all",   
          "addrType": "pre_allocated",
          "location": "all"
          }

     • To request Prisma Access to retrieve all pre-allocated IP addresses for Prisma Access gateways for a given location, enter the same information in the .txt file but substitute “all” with “gp_gateway” in the .txt file.
     • To request Prisma Access to retrieve all pre-allocated IP addresses for Prisma Access portals for a given location, enter the same information in the .txt file but substitute “all” with “gp_portal” in the .txt file.
   • Mobile Users—Explicit Proxy Deployments:
     To request that Prisma Access pre-allocate all IP addresses you need to add to allow lists for an explicit proxy deployment, enter the following text in the .txt file.

     {
     "actionType": "pre_allocate",
     "serviceType": "swg_proxy",
     "location": ["all"]
     }

   Palo Alto Networks recommends that you enter all so you can retrieve all required pre-allocated egress IP addresses to add to your allow lists.

   For Mobile Users—GlobalProtect deployments, the API command can return a large amount of information. To make the output more readable, if you have Python installed, you can add | python -m json.tool at the end of the cURL command.
5. Reenter this CURL command to retrieve the pre-allocated addresses.

   Prisma Access returns the information in the following format:

       "result": [
          {
               "zone": "prisma-access-zone1",
               "addresses": [
     ["ip-address1","ip-address2"]
               "zone_subnet" :  
     [subnet-and-mask1","subnet-and-mask2"]
               "address_details":[
                             {"address":"ip-address1",
                              "service_type":"service-type",                         
                               "addressType":"pre-allocated",
                              "expiring_in" : "validity-period" },
                             {"address":"ip-address2",
                              "service_type":"gp_gateway",
                              "addressType":"pre-allocated",
                              "validity_period_remaining" : "90 days" } ,        
            },        

   Where the variables represent the following API command output:

   Variable	Explanation
   prisma-access-zone1	The Prisma Access location for which pre-allocated IP addresses were retrieved.
   ip-address1 and ip-address2	The egress IP addresses that Prisma Access has pre-allocated for the specified location. Prisma Access retrieves two IP addresses for each location; you must add both of these IP addresses to your allow lists.
   subnet-and-mask1 and subnet-and-mask2	The subnets that Prisma Access has pre-allocated and reserved for the egress IP addresses in your deployment.
   service-type	The type of the pre-allocated egress IP address (either gp_portal for a Prisma Access portal or gp_gateway for a Prisma Access gateway).
   validity-period	The remaining time, in days, for which the pre-allocated IP address is valid. Onboard your mobile user location before the IP addresses’ validity period ends. If the pre-allocated IP addresses expire, you can rerun the API script to retrieve another set of pre-allocated IP addresses.

   You could receive an error if you attempt to pre-allocate IP addresses for locations that meet one of the following criteria:

   • You have already onboarded the location.
   • You onboarded, then deleted the location.
     In this case, enter the following text in the .txt file to retrieve the Mobile Users—GlobalProtect IP addresses for the location:

       {
     "serviceType": "gp_gateway",
     "addrType": "all",
     "location": "all"
        }

   • You have reached the maximum number of mobile user locations allowed by your license and can't add any more locations.
   • You entered the location name incorrectly.
   • You entered a serviceType other than gp_gateway.
   • you entered an actionType other than pre_allocate.

Set Up Prisma Access IP Address Change Notifications

  {"addrType": "public_ip", "addrChangeType": "add", "utc_timestamp": "2019-01-31 23:08:19.383894", "text": "Address List Change Notification"}

  {"addrType": "public_ip", "addrChangeType": "delete", "utc_timestamp": "2019-01-31 23:13:35.882151", "text": "Address List Change Notification"}

  {"addrType": "loopback_ip", "addrChangeType": "update", "utc_timestamp": "2019-01-31 23:29:27.100329", "text": "2018-05-11 23:29:27.100329"}

1. Go to ConfigurationNGFW and Prisma AccessConfiguration ScopePrisma AccessPrisma Access InfrastructureInfrastructure Settings.
2. Add an Egress IP Notification URL where you can be notified of IP address changes in your Prisma Access infrastructure.

   You can specify an IP address or an FQDN to an HTTP or HTTPS web service that is listening for change notifications. Prisma Access sends these notifications from the internet using a public IP address.

   You don't need to push your configuration for the notification URL to take effect.