<?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 Re: DNA Center internal API in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/dna-center-internal-api/m-p/4732641#M8834</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1394645"&gt;@dominiks&lt;/a&gt;&amp;nbsp;best practice would suggest not to use undocumented APIs, these might be left over from an older version in new versions to allow customer time to refactor code/apps. Using undocumented APIs is&lt;SPAN&gt;&amp;nbsp;time-consuming for everyone, and much more error-prone than working with a well-documented API. The end-result could be that your company uses/provides an API that is no fully tested, with functionality and security flaws etc.. I would open a TAC case or ask your AM for this to requested that engineering team comment on use of these.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Dec 2022 15:33:56 GMT</pubDate>
    <dc:creator>bigevilbeard</dc:creator>
    <dc:date>2022-12-05T15:33:56Z</dc:date>
    <item>
      <title>DNA Center internal API</title>
      <link>https://community.cisco.com/t5/network-platform-api/dna-center-internal-api/m-p/4732441#M8833</link>
      <description>&lt;DIV id="bodyDisplay" class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;
&lt;DIV class="lia-message-body-content"&gt;
&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;in addition to the "normal" Intent-API (&lt;A href="https://developer.cisco.com/docs/dna-center/" target="_blank"&gt;https://developer.cisco.com/docs/dna-center/&lt;/A&gt;) DNA Center uses some additional API calls for the representation of the web gui which are not documented. For example /api/assurance/v2/events or api/assurance/v1/host. So my questions are:&lt;/P&gt;
&lt;P&gt;1. Can i use these calls?&lt;/P&gt;
&lt;P&gt;2. Are these calls supported or won't be edited, so that they can be used in a project for a longer period?&lt;/P&gt;
&lt;P&gt;3. Are these calls documented or is there a plan to add them to the documentation?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind regards,&lt;BR /&gt;Dominik&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 05 Dec 2022 10:31:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/dna-center-internal-api/m-p/4732441#M8833</guid>
      <dc:creator>dominiks</dc:creator>
      <dc:date>2022-12-05T10:31:57Z</dc:date>
    </item>
    <item>
      <title>Re: DNA Center internal API</title>
      <link>https://community.cisco.com/t5/network-platform-api/dna-center-internal-api/m-p/4732641#M8834</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1394645"&gt;@dominiks&lt;/a&gt;&amp;nbsp;best practice would suggest not to use undocumented APIs, these might be left over from an older version in new versions to allow customer time to refactor code/apps. Using undocumented APIs is&lt;SPAN&gt;&amp;nbsp;time-consuming for everyone, and much more error-prone than working with a well-documented API. The end-result could be that your company uses/provides an API that is no fully tested, with functionality and security flaws etc.. I would open a TAC case or ask your AM for this to requested that engineering team comment on use of these.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Dec 2022 15:33:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/dna-center-internal-api/m-p/4732641#M8834</guid>
      <dc:creator>bigevilbeard</dc:creator>
      <dc:date>2022-12-05T15:33:56Z</dc:date>
    </item>
  </channel>
</rss>

