Hi Experts,
I’m facing issues with API call to update the LifeCycleState even though I have Scope set to all.
Has Anyone encountered similar issue?
Can you please post the link for the documentation you are referring to for this API call?
Here is the document I refer,
1 Like
Thanks for sharing the link @chandramohans27
Only thing I can think of is that the LCS ID you are using and the identity itself do not belong to the same Identity Profile. As you know when you try to change the LCS of an identity from UI, only options you get are the LCS list from the same Identity Profile.
Hope this helps
@iamnithesh Actually We have a workflow in place updating the LCS and doing further actions after updating LCS. Also I can confirm I’m using correct LCS ID to update the Identity from same Identity profile.
I was able to run this endpoint successfully on my tenant. Typically, a 403 HTTP response code is related to a permissions issue.
I also ran this using an invalid LCS ID and it seems to accept that input with no errors.
Are you sure that the PAT or access token is tied to an identity (User Context) and that the identity has the necessary permissions to make this change?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.