Palo Alto Networks Target API
Operations for managing scan targets (create, update, delete, list).
Operations 13
Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay
Ask an LLM
“How do I register a new target to scan?”
“Can I skip connection validation when creating a target?”
Tell an agent
Create a scan target named {name}.
Add target {name} of type {target_type} with description {description}.
Ask an LLM
“Which AI red-teaming scan targets have I configured?”
“Can I filter my scan targets by type or status?”
Tell an agent
List my scan targets.
Show scan targets of type {target_type} with status {status}.
Ask an LLM
“What configuration is stored for a particular scan target?”
“Can I see a target's connection parameters with secrets masked?”
Tell an agent
Show details for target {target_uuid}.
Get the full configuration of scan target {target_uuid}.
Ask an LLM
“Can I change a target's connection settings after creating it?”
“Is validation optional when I update an existing target?”
Tell an agent
Update target {target_uuid} and rename it to {name}.
Change the auth type of target {target_uuid} named {name} to {auth_type}.
Ask an LLM
“Can I permanently remove a scan target I no longer need?”
“Does deleting a target also wipe its encrypted configuration?”
Tell an agent destructive · confirm first
Delete scan target {target_uuid}.
Permanently remove target {target_uuid} and its stored config.
Ask an LLM
“Can I manually kick off profiling for a target?”
“What must a target have before profiling will start?”
Tell an agent
Start profiling target {target_uuid}.
Re-run the profiler on target {target_uuid} now.
Ask an LLM
“Can I edit a target's background and extra context without revalidating the connection?”
“Where do I add more context to a target's profile by hand?”
Tell an agent
Set the background of target {target_uuid} to {target_background}.
Add context {additional_context} to target {target_uuid}'s profile.
Ask an LLM
“What did profiling learn about my target?”
“Can I see the merged user and profiler data for a target?”
Tell an agent
Show profiling results for target {target_uuid}.
Get the profile data collected on target {target_uuid}.
Ask an LLM
“Can I send profiling questions to a target before saving it?”
“Is there a way to fill in a target's background automatically from probe answers?”
Tell an agent
Run profiling probes against target {name}.
Probe {name} with fields {probe_fields} and return the background it reports.
POST
/v1/target/validate-auth
Validate target auth credentials · Validate authentication configuration
#
Ask an LLM
“Can I check that OAuth2 credentials for a target actually work before saving?”
“Does auth validation test headers and basic auth, or only check fields are present?”
Tell an agent
Validate {auth_type} credentials {auth_config}.
Test the OAuth2 config {auth_config} by fetching a token, auth type {auth_type}.
POST
/v1/target/ms-copilot-studio/auth-url
Generate a Copilot Studio sign-in URL · Generate Copilot Studio auth URL
#
Ask an LLM
“How do I get the OAuth authorization URL for a Microsoft Copilot Studio target?”
“What client and tenant details does the Copilot Studio auth URL need?”
Tell an agent
Generate a Copilot Studio auth URL for client {client_id} in tenant {tenant_id} with secret {client_secret}.
Create the Microsoft Copilot Studio login link for target {target_uuid}, tenant {tenant_id}, client {client_id}, secret {client_secret}.
POST
/v1/target/ms-copilot-studio/token
Exchange a Copilot Studio auth code · Exchange Copilot Studio auth code
#
Ask an LLM
“After signing in to Copilot Studio, how do I turn the auth response into stored tokens?”
“Where are exchanged Copilot Studio tokens kept?”
Tell an agent
Exchange Copilot Studio auth response {auth_response} into token record {token_json_uuid} for client {client_id}, tenant {tenant_id}, secret {client_secret}.
Finish Copilot Studio login: store tokens under {token_json_uuid} from {auth_response} (client {client_id}, tenant {tenant_id}, secret {client_secret}).
DELETE
/v1/target/ms-copilot-studio/token/{token_json_uuid}
Delete Copilot Studio token records · Delete MS Copilot Studio token records
#
Ask an LLM
“If I cancel a Copilot Studio setup, how do I clean up the stored tokens?”
“Can I remove both the auth flow and token cache records for Copilot Studio?”
Tell an agent destructive · confirm first
Delete Copilot Studio token records {token_json_uuid}.
Clean up the cancelled Copilot Studio sign-in {token_json_uuid}.