Well, I've already explained why an API (and hence its endpoints) isn't a CI itself before. They don't meet the definitions.
API as a product though - I'd qualify that as "a component of a product", but yes, they should be considered as products. I mean, an API on its own is not a product because it's utterly useless without the thing it is an interface to, but it's certainly a distinct part of a product. (Just thinking of Jira, you've got Jira, the java API, the REST API, and then all the other bits - Java and REST APIs for Software, Service Management, Insight, Advanced roadmaps and so on)
I got this definition from IBM, and I think APIs has the characteristics :
A configuration item (CI) is any service component, infrastructure element, or other item that needs to be managed in order to ensure the successful delivery of services.
Each CI has several characteristics:
CIs vary in complexity, size, and type. They can range from an entire service, which may consist of hardware, software, and documentation, to a single program module or a minor hardware component. The lowest-level CI is usually the smallest unit that will be changed independently of other components.
And there you go - the API does not have a variation of classification, a status, relationships with other things or an owner (beyond it belonging to the system you are in). They are not even configured in any way.
I am not sure you really mean "API" now.
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events