# WebServices: Create Account/Add Entitlement operations **URL:** \ **Category:** IIQ Discussion and Questions\ **Tags:** webservice-connector, access-requests, rules, roles, entitlements, identityiq, connectors, provisioning, apis\ **Created:** [August 25, 2025, 7:19pm UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212 "2025-08-25T19:19:57Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![sonali\_manhas](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@sonali\_manhas](https://developer.sailpoint.com/discuss/u/sonali_manhas)\ **Post date:** [August 25, 2025, 7:19pm UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212/1 "2025-08-25T19:19:57Z")
## Which IIQ version are you inquiring about? 8.4p1 ## Please share any images or screenshots, if relevant. ![Screenshot 2025-08-25 151259](https://global.discourse-cdn.com/sailpoint/original/3X/3/2/32a57d7e6b76225e5629c0686421e5df6deff66e.png) ## Share all details about your problem, including any error messages you may have received. Hi Developer Forum, For a WebService application: **Scenario: Raise an access request for multiple entitlements \> results in Account Creation.** API only supports a single entitlement i.e. an account can only be created with one entitlement/an account can only be added with one entitlement. Endpoints for Create Account and Add Entitlement operation are the same. **Observations:** Since the Admin role was approved first, that item was provisioned first as part of Create Account operation and the Get Object operation updates the id returned from the API. For the second Viewer role, the Add Entitlement operation is called second, and is provisioned to the user. Once the Perform Identity Request Maintenance task is executed, this is how the request looks. The entitlement which was provisioned shows up as Failed in the access request. (As shown in the screenshot) Any pointers? ---
**Author:** ![enistriminsait](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@enistriminsait](https://developer.sailpoint.com/discuss/u/enistriminsait)\ **Post date:** [August 25, 2025, 8:21pm UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212/2 "2025-08-25T20:21:26Z")
Hi @sonali_manhas, into the after op. rule of creation operation you can read the plan and launch a an api call to add each entitlement. ---
**Author:** ![sonali\_manhas](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@sonali\_manhas](https://developer.sailpoint.com/discuss/u/sonali_manhas)\ **Post date:** [August 25, 2025, 9:40pm UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212/3 "2025-08-25T21:40:58Z")
Thank you for replying Emanuele! The issue is that even though the Add Entitlement operation is called and entitlement is provisioned successfully, the status of the entitlement is Failed in the access request. ---
**Author:** ![enistriminsait](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@enistriminsait](https://developer.sailpoint.com/discuss/u/enistriminsait)\ **Post date:** [August 25, 2025, 10:41pm UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212/4 "2025-08-25T22:41:42Z")
which error do you have? ---
**Author:** ![paul\_hilchey](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/paul_hilchey/32/24080_2.png) [@paul\_hilchey](https://developer.sailpoint.com/discuss/u/paul_hilchey)\ **Post date:** [August 26, 2025, 3:41am UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212/5 "2025-08-26T03:41:37Z")
Hi @sonali_manhas, if I’m understanding correctly, the application does support a user having multiple values for an entitlement, but the api only allows adding one value at a time. Check your application xml and see if “addRemoveEntInSingleReq” is set or not. ---
**Author:** ![sonali\_manhas](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@sonali\_manhas](https://developer.sailpoint.com/discuss/u/sonali_manhas)\ **Post date:** [August 26, 2025, 1:34pm UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212/7 "2025-08-26T13:34:32Z")
No errors. Just that the Provisioning Status shows as Failed in the access request, as shown in the screenshot. ---
**Author:** ![sonali\_manhas](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@sonali\_manhas](https://developer.sailpoint.com/discuss/u/sonali_manhas)\ **Post date:** [August 28, 2025, 3:03pm UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212/8 "2025-08-28T15:03:58Z")
This was resolved by configuring the identity attribute for the account schema as an actual identity attribute (for example: email), whose value will be available, instead of an id generated from the target side. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [October 27, 2025, 3:04pm UTC](https://developer.sailpoint.com/discuss/t/webservices-create-account-add-entitlement-operations/173212/9 "2025-10-27T15:04:54Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.