Reply from a community member, 31 March 2025

Hi Christina,

I'm not 100%, but my understanding of the API is that this would not cause a problem - I don't think there is any differentiation/limitation of multiple API calls from different places beyond the (from memory) 60 calls a minute and pagination/limits in responses that are detailed in the Litmos documentation. Although we don't use the API significantly for user data, we have multiple sets of calls/queries from different places in addition to some semi-automated use via Postman without a problem here.

Assuming these are custom created API calls, my only comments would be:

1. To be mindful of the rate limits for the API and minimise/avoid crossover between the 2 API runs to stay below the limits.
2. Be aware about exactly what data each API call is providing e.g. keep using Okta as the "source of truth" for the majority of your user data, and only use UKG Pro to update active/inactive status and the other items as needed. Otherwise you may open up opportunities for data conflicts e.g. "Name/Job Title/Department etc is X in Okta, Y in UKG Pro" and the data keeps swapping depending on which system most recently ran a call, if your data is not perfect in both!

Reply from a community member, 31 March 2025

Couple of additional thoughts...

• Make sure that the required user data to update a user is identical in both systems (first name, last name, username?) so that both systems update the same user account and you don't get duplicate/multiple accounts etc.
• Is there a way to disable active/inactive status from Okta? There is potential for conflict here (e.g. Okta says "this person is active", UKG Pro says "this person is inactive"). Ties into point 2 above.