Given, IdentityNow has a wide range of API’s available, is there an easy way to monitor the consumption of these api’s and if there are limits to which customer should be aware of (and what happens when the limits are breached if any 
)
I believe this message should be under the IdentityNow category, so answering with that in mind…:
The use of APIs is not limited to external use, but there is a lot of interaction between the UI and the backend via these APIs as well. In other words, a huge amount of calls to keep track of. Currently, I’m not aware of any customer facing feature that keeps track of these interactions or provides statistics thereof. May I suggest to post an idea for this on Compass?
Regarding limitations, yes there are. There is rate limiting on the API, which you shouldn’t hit under normal circumstances, but these will protect the platform against attacks
- Menno Pieters
2 Likes
Hey @shashikantshetty,
Thank you for joining the forum and for posting this question! I have moved your question over to the IDN category where it can be more easily found by other developers that have similar questions. 
Every request is given a request ID. It is visible in My Requests, and it is also seen administratively in Search > Account Activity by searching on the request ID.
In general - the API endpoint will respond with a standard ‘429 - Too many requests’ error when a large amount of requests are received in a short duration. The 429 response should also include a ‘Retry-After’ header value that indicates how long a client should pause before attempting the request again. Including error handling for this type of response would create a more robust integration.
1 Like