For one of my applications, we use a delimited file source for aggregating accounts and entitlements. However, for provisioning after access request approval, the requirement is to use an API to provision directly to the application, no manual provisioning or creating ticket.
Is it possible to use API-based provisioning for an application that uses a delimited file source for aggregation? My understanding is that in such cases, only manual provisioning is typically supported. However, I’d like to explore if there are any workarounds or configurations that would allow us to use API-based provisioning instead.
Is the API you’re referring to meant for creating accounts within the SailPoint tenant, or is it for provisioning accounts in the target application? My requirement is to create or update an account in the target application by invoking its APIs after an access request for that account has been approved. The accounts are aggregated using a delimited file connector.
If the application supports API based provisioning, then why to go for delimited connector? We can onboard that application using web services connector.
API suggested by @kdfreeman for account creation for delimited connector can be created within SailPoint but not on target application.