Integrating the beta load accounts API with a web services connector

[danielgoldston98 (Daniel Goldston)]

Has anyone integrated /beta/sources/:id/load-accounts with a Web Service connector?

We essentially need to run the API on a test/account aggregation operation. This will start an unoptimized aggregation on another source in the tenant.

The issue we are facing with the new API is that when the content type is multipart/form-data we receive a 500 error.

I can get this API to work in Bruno with the content type set to multipart/form-data. However, when the request is sent the content type calculates a boundary e.g content-type: multipart/form-data; boundary=--------------------------example

[ashutosh08 (Ashutosh Singh)]

Hi @danielgoldston98,

How are you triggering this API, from before operation rule?

Thanks

[dopstrick (Dylan Strickland)]

You could also use workflows:

trigger: Account Aggregation Completed (filter on your webservices account)
action: HTTP request (call the beta loadAccounts end point).

[tdelorge-mmb (Thomas DELORGE)]

Hello Dylan,

See Colin’s answer for this scenario (POST /api/source/loadAccounts - #123 by colin_mckibben) : not possible at this time,

@danielgoldston98 : I will give a look to this scenario this week or next on, will keep you on if I found something interesting

[danielgoldston98 (Daniel Goldston)]

Hi @ashutosh08,

The API is triggered on an account aggregation operation in a web services source (Not using a before-operation rule). Once we start an aggregation on the web services source, it calls the API which runs an aggregation on another source. This currently works but we can’t get the aggregation to have disable optimization set to true. It would be great if the API worked for content type x-www-form-urlencoded.

Thanks,
Dan

[jsosa (Julian Sosa)]

Hi Daniel, I am. Working here, but when using inside http request action on a workflow, aggregation performs optimized (and of course disableOptimization is sending with true value). Triggering from postman works right.

[angelo_mekenkamp]

Hi Daniel,

Out of curiosity, have you tried using the Curl functionality on the web services connector?

General Information

If you see the http request in postman, you can see the request in curl format in postman, and try to copy this to the web service connector.

I haven’t tried this myself, but since curl supports passing form data and since the web service connector support curl. I wonder if this means that SailPoint also supports passing form data to through the curl account.