<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Wildfire API &amp;quot;Missing required field apikey&amp;quot; in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/wildfire-api-quot-missing-required-field-apikey-quot/m-p/557407#M3432</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have been working on automating our internal URL analysis process, and I've been using the following documentation to get the verdict of a URL via the Wildfire API:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/wildfire/u-v/wildfire-api/get-wildfire-information-through-the-wildfire-api/get-a-wildfire-verdict-wildfire-api" target="_blank"&gt;Get a WildFire Verdict (WildFire API) (paloaltonetworks.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;When using&amp;nbsp;&lt;STRONG&gt;Example Request 2&amp;nbsp;&lt;/STRONG&gt;in the above link, I replace the placeholder API value (&lt;SPAN&gt;&amp;lt;API KEY&amp;gt;) with my own and keep the rest of the cURL request the same. However, when doing this I receive the following HTTP response:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;lt;error&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;error-message&amp;gt;'Missing required field apikey'&amp;lt;/error-message&amp;gt;&lt;BR /&gt;&amp;lt;/error&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Attached is a screenshot of my cURL request (with the redacted API keys). Thanks in advance!&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Sep 2023 18:33:51 GMT</pubDate>
    <dc:creator>chughey</dc:creator>
    <dc:date>2023-09-11T18:33:51Z</dc:date>
    <item>
      <title>Wildfire API "Missing required field apikey"</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/wildfire-api-quot-missing-required-field-apikey-quot/m-p/557407#M3432</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have been working on automating our internal URL analysis process, and I've been using the following documentation to get the verdict of a URL via the Wildfire API:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/wildfire/u-v/wildfire-api/get-wildfire-information-through-the-wildfire-api/get-a-wildfire-verdict-wildfire-api" target="_blank"&gt;Get a WildFire Verdict (WildFire API) (paloaltonetworks.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;When using&amp;nbsp;&lt;STRONG&gt;Example Request 2&amp;nbsp;&lt;/STRONG&gt;in the above link, I replace the placeholder API value (&lt;SPAN&gt;&amp;lt;API KEY&amp;gt;) with my own and keep the rest of the cURL request the same. However, when doing this I receive the following HTTP response:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;lt;error&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;error-message&amp;gt;'Missing required field apikey'&amp;lt;/error-message&amp;gt;&lt;BR /&gt;&amp;lt;/error&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Attached is a screenshot of my cURL request (with the redacted API keys). Thanks in advance!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Sep 2023 18:33:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/wildfire-api-quot-missing-required-field-apikey-quot/m-p/557407#M3432</guid>
      <dc:creator>chughey</dc:creator>
      <dc:date>2023-09-11T18:33:51Z</dc:date>
    </item>
    <item>
      <title>Re: Wildfire API "Missing required field apikey"</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/wildfire-api-quot-missing-required-field-apikey-quot/m-p/559542#M3439</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/314895"&gt;@chughey&lt;/a&gt;, getting a verdict uses&amp;nbsp;&lt;FONT face="courier new,courier"&gt;/get/verdict/&lt;/FONT&gt;, but the screenshot shows &lt;FONT face="courier new,courier"&gt;/submit/link&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Please try the correct API endpoint first, and see if that helps&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;curl -F 'apikey=1234567890' -F 'url=&lt;A href="https://www.google.com" target="_blank"&gt;https://www.google.com&lt;/A&gt;' '&lt;A href="https://wildfire.paloaltonetworks.com/publicapi/get/verdict" target="_blank"&gt;https://wildfire.paloaltonetworks.com/publicapi/get/verdict&lt;/A&gt;'&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;wildfire&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;get-verdict-info&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;url&amp;gt;&lt;A href="https://www.google.com" target="_blank"&gt;https://www.google.com&lt;/A&gt;&amp;lt;/url&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;verdict&amp;gt;0&amp;lt;/verdict&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;analysis_time&amp;gt;2023-09-25T13:15:05Z&amp;lt;/analysis_time&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;valid&amp;gt;Yes&amp;lt;/valid&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;/get-verdict-info&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;lt;/wildfire&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Sep 2023 16:05:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/wildfire-api-quot-missing-required-field-apikey-quot/m-p/559542#M3439</guid>
      <dc:creator>JimmyHolland</dc:creator>
      <dc:date>2023-09-26T16:05:21Z</dc:date>
    </item>
  </channel>
</rss>

