It really depends on what options you are ok with.
One potential solution could be to create a separate Delimited Text source that will hold the ticket information. This source can then be setup as the source for an identity attribute and thus can be synced to AD.
The Accounts API (Accounts | SailPoint Developer Community) allows you to manage Accounts in a Delimited Text source, so you could insert / update an account using the same workflow.
Thank you @sauvee . I have thought of this solution but maintaining this new delimited source upto date with flow of new users is another overhead we are trying to avoid.
We have another workaround to use create account API using the response through get API and use create operation to update attribute. (This would work irrespective of source type) but at the same time it might create data discrepancy on users reference ID in IDN.