Monitoring API call

Hello everyone,

I’m wondering if there’s a way in Identity Security Cloud to notify someone via email that the account creation was unsuccessful if a provisioning operation performed with the “POST Create Account - v3//accounts” call results in a 400, 409, or 500 result from this API.

Thank you very much.

Hi @vcarelli

Are you trying to monitor the API call results within a workflow, or are you tracking account creation when a direct connect source (e.g., AD) provisions the account using the ‘Create Account’ policy?

If it’s the latter, you can subscribe to a saved search following the instructions in this Subscribing to Saved Searches. ISC can be configured to automatically send emails on a set schedule containing the results of the saved search query. You can customize the frequency of these emails and specify the recipients.

Search query example:
technicalName:"ACCOUNT_CREATE_FAILED" AND type:"PROVISIONING"

If you are using a workflow to create accounts, you can use the ‘Compare Numbers’ operator to check the result returned by the API call, and then use the ‘Send Email’ action to notify you.

Hope this would help.

1 Like

You can use a Workflow with Provisioning Completed Trigger to send real time failure notifications.

If it is ok to have consolidated failures, you can subscribe to search query as already mentioned by Noor in the above response.

2 Likes

Let me explain the context better.
We have a source on IdentityNow, Flat File, which we populate with an API call when the customer needs to register a new account.
Then it launches the creation API (which is proxied) and then the call. If it shows a 200 as successful creation on SailPoint, is it possible to monitor, or better yet, send an alert email, when the call returns an error of 400 or 500?

What platform is making the API call to /accounts to create the flat file accounts? It seems to me that it should have a way to evaluate the API response. If it really is just a fire and forget, then maybe it can call an external trigger on a workflow in ISC, passing the account data in the message payload, and then use the workflow to call the /accounts API. The workflow can evaluate the API response and follow a different path based on the status being 2** or 4** which could include sending an email.

The platform that makes the /accounts API calls is a custom application developed internally. This application integrates the SailPoint APIs and autonomously manages the account creation operations in a flat format.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.