<?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 Cortex XSIAM API to get available custom fields in incident in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/cortex-xsiam-api-to-get-available-custom-fields-in-incident/m-p/1223271#M123558</link>
    <description>&lt;P&gt;We have an api to update an incident, in it we can also set values for the custom fields we created in the UI.&lt;BR /&gt;&lt;BR /&gt;POST &lt;BR /&gt;&lt;SPAN&gt;&lt;A href="https://api-" target="_blank"&gt;https://api-&lt;/A&gt;&amp;lt;fqdn&amp;gt;/public_api/v1/incidents/update_incident&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;BODY&lt;BR /&gt;{&lt;BR /&gt;"request_data": {&lt;BR /&gt;"incident_id": "&amp;lt;incident_id&amp;gt;",&lt;BR /&gt;"update_data": {&lt;BR /&gt;"field_1": " field_1_value",&lt;BR /&gt;"field_2": "field_2_value"&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;Is there an API to get a list of custom fields available for a console, that would return field_1, field_2 ....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 08 Mar 2025 11:33:35 GMT</pubDate>
    <dc:creator>iawan</dc:creator>
    <dc:date>2025-03-08T11:33:35Z</dc:date>
    <item>
      <title>Cortex XSIAM API to get available custom fields in incident</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cortex-xsiam-api-to-get-available-custom-fields-in-incident/m-p/1223271#M123558</link>
      <description>&lt;P&gt;We have an api to update an incident, in it we can also set values for the custom fields we created in the UI.&lt;BR /&gt;&lt;BR /&gt;POST &lt;BR /&gt;&lt;SPAN&gt;&lt;A href="https://api-" target="_blank"&gt;https://api-&lt;/A&gt;&amp;lt;fqdn&amp;gt;/public_api/v1/incidents/update_incident&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;BODY&lt;BR /&gt;{&lt;BR /&gt;"request_data": {&lt;BR /&gt;"incident_id": "&amp;lt;incident_id&amp;gt;",&lt;BR /&gt;"update_data": {&lt;BR /&gt;"field_1": " field_1_value",&lt;BR /&gt;"field_2": "field_2_value"&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;Is there an API to get a list of custom fields available for a console, that would return field_1, field_2 ....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 08 Mar 2025 11:33:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cortex-xsiam-api-to-get-available-custom-fields-in-incident/m-p/1223271#M123558</guid>
      <dc:creator>iawan</dc:creator>
      <dc:date>2025-03-08T11:33:35Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XSIAM API to get available custom fields in incident</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cortex-xsiam-api-to-get-available-custom-fields-in-incident/m-p/1223281#M123560</link>
      <description>&lt;P&gt;Yes! You can retrieve the list of custom fields available in your Cortex XSIAM or XDR console using the &lt;STRONG data-start="104" data-end="128"&gt;Get Incidents Fields&lt;/STRONG&gt; API. This API provides metadata about the available fields, including custom fields.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;API Endpoint :POST &lt;A href="https://api-&amp;lt;fqdn&amp;gt;/public_api/v1/incidents/get_fields" target="_blank"&gt;https://api-&amp;lt;fqdn&amp;gt;/public_api/v1/incidents/get_fields&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Request Body&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="hljs-punctuation"&gt;{&lt;/SPAN&gt; &lt;SPAN class="hljs-attr"&gt;"request_data"&lt;/SPAN&gt;&lt;SPAN class="hljs-punctuation"&gt;:&lt;/SPAN&gt; &lt;SPAN class="hljs-punctuation"&gt;{&lt;/SPAN&gt;&lt;SPAN class="hljs-punctuation"&gt;}&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="hljs-punctuation"&gt;&amp;nbsp; &amp;nbsp;}&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-start="362" data-end="411"&gt;No parameters are required in the request body.)&lt;/P&gt;
&lt;H3 data-start="413" data-end="437"&gt;&lt;STRONG data-start="417" data-end="437"&gt;Response Example&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P data-start="438" data-end="584"&gt;If successful, the API will return a list of fields, including both &lt;STRONG data-start="506" data-end="517"&gt;default&lt;/STRONG&gt; and &lt;STRONG data-start="522" data-end="532"&gt;custom&lt;/STRONG&gt; fields. The response will look something like this:&lt;/P&gt;
&lt;P data-start="438" data-end="584"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="438" data-end="584"&gt;{&lt;BR /&gt;"reply": {&lt;BR /&gt;"fields": [&lt;BR /&gt;{&lt;BR /&gt;"name": "field_1",&lt;BR /&gt;"description": "Custom Field 1",&lt;BR /&gt;"is_custom": true&lt;BR /&gt;},&lt;BR /&gt;{&lt;BR /&gt;"name": "field_2",&lt;BR /&gt;"description": "Custom Field 2",&lt;BR /&gt;"is_custom": true&lt;BR /&gt;},&lt;BR /&gt;{&lt;BR /&gt;"name": "status",&lt;BR /&gt;"description": "Incident Status",&lt;BR /&gt;"is_custom": false&lt;BR /&gt;}&lt;BR /&gt;]&lt;BR /&gt;}&lt;BR /&gt;}&lt;/P&gt;
&lt;P data-start="438" data-end="584"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="438" data-end="584"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="438" data-end="584"&gt;other points&lt;/P&gt;
&lt;P data-start="438" data-end="584"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="438" data-end="584"&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI data-start="994" data-end="1067"&gt;Look for fields where &lt;CODE data-start="1018" data-end="1037"&gt;"is_custom": true&lt;/CODE&gt;—these are your custom fields.&lt;/LI&gt;
&lt;LI data-start="1068" data-end="1152"&gt;The &lt;CODE data-start="1074" data-end="1082"&gt;"name"&lt;/CODE&gt; value is what you should use in your &lt;STRONG data-start="1120" data-end="1139"&gt;update_incident&lt;/STRONG&gt; API request.&lt;/LI&gt;
&lt;LI data-start="1153" data-end="1212"&gt;The &lt;CODE data-start="1159" data-end="1174"&gt;"description"&lt;/CODE&gt; provides the label as seen in the UI.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 09 Mar 2025 03:08:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cortex-xsiam-api-to-get-available-custom-fields-in-incident/m-p/1223281#M123560</guid>
      <dc:creator>Mudhireddy</dc:creator>
      <dc:date>2025-03-09T03:08:52Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XSIAM API to get available custom fields in incident</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cortex-xsiam-api-to-get-available-custom-fields-in-incident/m-p/1223294#M123570</link>
      <description>&lt;P&gt;Unfortunately that endpoint is not working, I have tried it with multiple instances, getting the same error.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Error Code: 500&lt;BR /&gt;Internal Server Error&lt;/P&gt;
&lt;P&gt;The server encountered an unexpected internal server error&lt;/P&gt;
&lt;P&gt;(generated by waitress)&lt;/P&gt;</description>
      <pubDate>Sun, 09 Mar 2025 10:32:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cortex-xsiam-api-to-get-available-custom-fields-in-incident/m-p/1223294#M123570</guid>
      <dc:creator>iawan</dc:creator>
      <dc:date>2025-03-09T10:32:01Z</dc:date>
    </item>
  </channel>
</rss>

