# Search API Entitlement Information For A Particular Identity

**URL:** <https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848>\
**Category:** SHF Discussion and Questions\
**Tags:** workflows, entitlements, apis, sailpoint-identity-security\
**Created:** [April 24, 2024, 1:58pm UTC](https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848 "2024-04-24T13:58:37Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![kdfreeman](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kdfreeman/32/22737_2.png) [@kdfreeman](https://developer.sailpoint.com/discuss/u/kdfreeman)\
**Post date:** [April 24, 2024, 1:58pm UTC](https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848/1 "2024-04-24T13:58:37Z")

</div>

Hello Experts,

I have a scenario where I have to design a workflow where I pull an identity for a specific trigger condition and then fetch user’s entitlement metadata on a particular source only. And use that metadata information [metadata have email information] from the entitlement to send email to another person. I was planning to use Search API to fetch user information and pull the entitlement metadata, but it seems search API is not pulling entitlement metadata at all.

Is there any way I can pull entitlement metadata in workflow HTTP request and use that information in next workflow steps?

Any help would be appreciated.

---

<div class="post-metadata">

**Author:** ![Shanmukh](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@Shanmukh](https://developer.sailpoint.com/discuss/u/Shanmukh)\
**Post date:** [April 24, 2024, 2:47pm UTC](https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848/2 "2024-04-24T14:47:09Z")

</div>

Hi @kdfreeman,

You can use [get-entitlement | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/beta/get-entitlement) beta API to get the entitlement meta data of any entitlement based on the UUID of the entitlement.

You can configure this API as a HTTP request in your workflow by passing the input as the UUID of the entitlement that is present for the user and get the metadata as the response of this action.

Thank you.  
Shanmukh

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/42445_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [April 24, 2024, 5:38pm UTC](https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848/3 "2024-04-24T17:38:31Z")

</div>

> [@kdfreeman](#):
>
> it seems search API is not pulling entitlement metadata at all

All Entitlements, Access Profiles and Roles are returned inside an array named “access” in Search API response. Here is a typical ENTITLEMENT

```auto
"access": [
	{
		"requestCommentsRequired": false,
		"schema": "group",
		"cloudEligible": false,
		"displayName": "Everyone",
		"standalone": true,
		"source": {
			"name": ".......................",
			"id": "........................."
		},
		"type": "ENTITLEMENT",
		"enabled": false,
		"privileged": false,
		"name": "Everyone",
		"disabled": false,
		"id": "..............................",
		"requestable": false,
		"attribute": "groups",
		"value": "..............................",
		"cloudGoverned": false
	},
        ....
]

```

---

<div class="post-metadata">

**Author:** ![kdfreeman](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kdfreeman/32/22737_2.png) [@kdfreeman](https://developer.sailpoint.com/discuss/u/kdfreeman)\
**Post date:** [April 24, 2024, 5:54pm UTC](https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848/4 "2024-04-24T17:54:22Z")

</div>

@iamnithesh , Exactly. I was planning to use the entitlement info inside Access array. But, what I am looking is the metadata of the entitlement. Using search API, metadata is not pulling in the entitlement information. Only name and value can be seen of the entitlement.

When you use get Entitlement API using ID, you can see metadata info as well of that particular entitlement. But not from search API.

---

<div class="post-metadata">

**Author:** ![vkashat](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/vkashat/32/9721_2.png) [@vkashat](https://developer.sailpoint.com/discuss/u/vkashat)\
**Post date:** [April 24, 2024, 5:57pm UTC](https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848/5 "2024-04-24T17:57:40Z")

</div>

Hi @kdfreeman

It seems you may have to combine the suggestions from the previous comments to get what you need, use the search API to get the entitlement IDs, then use loop over those and use the get-entitlement API to get the metadata.

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/42445_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [April 24, 2024, 5:58pm UTC](https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848/6 "2024-04-24T17:58:54Z")

</div>

Are you able to filter the required entitlement from the response from Identity Search? If so, you can send another request to Entitlement API with the `id` to fetch full details

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [June 23, 2024, 5:59pm UTC](https://developer.sailpoint.com/discuss/t/search-api-entitlement-information-for-a-particular-identity/53848/7 "2024-06-23T17:59:06Z")

</div>

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