# Pega Traditional APIs

**URL:** <https://forums.pega.com/t/pega-traditional-apis/11088>\
**Category:** General\
**Tags:** dx-api, smart-dispute-for-issuers, case-management\
**Created:** [March 11, 2026, 4:40pm UTC](https://forums.pega.com/t/pega-traditional-apis/11088 "2026-03-11T16:40:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gil\_BC](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/gil_bc/32/6350_2.png) [@Gil\_BC](https://forums.pega.com/u/Gil_BC)\
**Post date:** [March 11, 2026, 4:40pm UTC](https://forums.pega.com/t/pega-traditional-apis/11088/1 "2026-03-11T16:40:08Z")

</div>

Hello everyone, has anyone here worked implementing the processing of cases using Traditional APIS? specifically performing the assignment, I would like to check how to override the temporary user Pega creates on every interaction on the case, since it logs like a dynamic requestor or operator ID, not sure where does it come. It is something like “AU65088….”.

I changed the Service Package to use an OAuth 2.0 client to use the APIs. Any ideas?

Thanks in Advance,

Gilberto

---

<div class="post-metadata">

**Author:** ![RameshSangili](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/rameshsangili/32/23377_2.png) [@RameshSangili](https://forums.pega.com/u/RameshSangili)\
**Post date:** [March 11, 2026, 7:31pm UTC](https://forums.pega.com/t/pega-traditional-apis/11088/2 "2026-03-11T19:31:34Z")

</div>

This is because that you configured OAuth Client Credentials with Access group, so Pega dynamically creates the temporary operator for every request on the fly.

---

<div class="post-metadata">

**Author:** ![Gil\_BC](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/gil_bc/32/6350_2.png) [@Gil\_BC](https://forums.pega.com/u/Gil_BC)\
**Post date:** [March 11, 2026, 11:47pm UTC](https://forums.pega.com/t/pega-traditional-apis/11088/3 "2026-03-11T23:47:10Z")

</div>

Ok, thanks for your answer. 🤔 Probably we will need to change that configuration, since several processes will access the API to perform assignment, and we need to track which of the processes performed the action due to some requirements to measure performance on working cases. I think we need to explore the other options for the Authentication.

Any suggestion from anyone will be appreciated 😄 .