# API Bulk Search campaign Certification assigned to entitlement owner

**URL:** <https://developer.sailpoint.com/discuss/t/api-bulk-search-campaign-certification-assigned-to-entitlement-owner/157699>\
**Category:** SHF Discussion and Questions\
**Tags:** identity-security-cloud\
**Created:** [July 19, 2025, 1:55am UTC](https://developer.sailpoint.com/discuss/t/api-bulk-search-campaign-certification-assigned-to-entitlement-owner/157699 "2025-07-19T01:55:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![YEMA](https://avatars.discourse-cdn.com/v4/letter/y/ba8739/32.png) [@YEMA](https://developer.sailpoint.com/discuss/u/YEMA)\
**Post date:** [July 19, 2025, 1:55am UTC](https://developer.sailpoint.com/discuss/t/api-bulk-search-campaign-certification-assigned-to-entitlement-owner/157699/1 "2025-07-19T01:55:07Z")

</div>

Dear experts,

May I ask is there a way to call API to bulk create Certification and assign to entitlement owner?

So I have tried using API to create Search Campaign and could successfully create a campaign and assign to individual. However, we have too many entitlements and each has different owner as reviewer. In addition, we need to generate a general report for all certification, so if they are too many, then we need a lot of manual work.

I searched on the documentation, it says that we could have a rule setting in SailPoint tenant to route the certification campaign to entitlement owner, but I don’t know how to configure that.

Remark: We are not allowed to reassign the certification.

Please let me know if you have any ideas related to this.

---

<div class="post-metadata">

**Author:** ![HussainshaSyed001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/hussainshasyed001/32/28234_2.png) [@HussainshaSyed001](https://developer.sailpoint.com/discuss/u/HussainshaSyed001)\
**Post date:** [July 19, 2025, 6:01am UTC](https://developer.sailpoint.com/discuss/t/api-bulk-search-campaign-certification-assigned-to-entitlement-owner/157699/2 "2025-07-19T06:01:35Z")

</div>

this can be achieved with the help of automation scripts either by ruby or python and even isc python sdk. See the following doc that helps us to make script:

> **[Certification\_Campaigns | SailPoint Developer Community](https://developer.sailpoint.com/docs/tools/sdk/python/v2025/methods/certification-campaigns/)**
>
> Use this API to implement certification campaign functionality.

---

<div class="post-metadata">

**Author:** ![mcheek](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mcheek/32/23705_2.png) [@mcheek](https://developer.sailpoint.com/discuss/u/mcheek)\
**Post date:** [July 19, 2025, 11:48am UTC](https://developer.sailpoint.com/discuss/t/api-bulk-search-campaign-certification-assigned-to-entitlement-owner/157699/3 "2025-07-19T11:48:39Z")

</div>

SailPoint had announced this capability was “coming soon” over 6 months ago, but nothing has seemed to materialize yet

> [@New Capability: SailPoint next generation certification](https://developer.sailpoint.com/discuss/t/new-capability-sailpoint-next-generation-certification/92674/32):
>
> Hello Everyone, Is this feature available. I don’t see it in our tenant. If not, when can we expect this to be available?

Currently, the workaround is to assign the certification to a single identity and use a script to reassign the individual tasks to their respective owners.

However, seeing this

> [@YEMA](#):
>
> Remark: We are not allowed to reassign the certification.

It doesn’t seem like that would work for you. I’m curious what the reason behind that is

---

<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:** [September 17, 2025, 11:48am UTC](https://developer.sailpoint.com/discuss/t/api-bulk-search-campaign-certification-assigned-to-entitlement-owner/157699/4 "2025-09-17T11:48:52Z")

</div>

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