This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About mteachout
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About mteachout
02-13-2021
2Posts
0Likes
0Solutions
Feb 13, 2021Last Visited
User
Activity
User
Profile
Latest posts by mteachout
| Subject | Views | Posted |
|---|---|---|
| 4077 | 01-08-2021 08:03 AM | |
| 10478 | 02-18-2019 10:31 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 3 Likes | |||
| 2 Likes | |||
| 1 Like |
User Badges
Community Statistics
| Member Since | 03-29-2016 08:16 AM |
| Date Last Visited | 02-13-2021 08:59 AM |
| Posts | 2 |
01-08-2021
08:03 AM
I ran into this as well. For me, the fix was updating the API_KEY_ID that was in the headers. That was mismatched with the value found in the ID column under API Keys. curl -X POST https://api-{fqdn}/public_api/v1/endpoints/delete/ \ -H "x-xdr-auth-id:{API_KEY_ID}" \ -H "Authorization:{API_KEY}" \ -H "Content-Type:application/json" \
... View more
- Tags:
- api
02-18-2019
10:31 AM
What was the fix? Is it something you had to change or is it included in a later release?
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
02-13-2021
08:59 AM
|
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks