DNA Center internal API

[dominiks]

Hello,

in addition to the "normal" Intent-API (https://developer.cisco.com/docs/dna-center/) 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:

1. Can i use these calls?

2. Are these calls supported or won't be edited, so that they can be used in a project for a longer period?

3. Are these calls documented or is there a plan to add them to the documentation?

Kind regards,
Dominik

[dominiks]

Hello,

in addition to the "normal" Intent-API (https://developer.cisco.com/docs/dna-center/) 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:

1. Can i use these calls?

2. Are these calls supported or won't be edited, so that they can be used in a project for a longer period?

3. Are these calls documented or is there a plan to add them to the documentation?

Kind regards,
Dominik

[bigevilbeard]

@dominiks 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 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.

Hope this helps.