Hi All, kindly provide any inputs if possible.

@VenkatTiyyagura

Yes, do it inside the same connector call. Configure an OAuth 2.0 Authentication Profile on your Connect-REST so Pega automatically adds Authorization: Bearer <token>. Then add a request Data Transform (or pre-activity) on the connector and read the already-resolved OAuth token, and set your second header there, e.g., X-Auth-Token = "Bearer " + <access token>. This avoids a separate data page call and keeps token reuse/refresh handled by the Authentication Profile cache. If you must fetch it explicitly, call the profile’s token data page/function to get pyAccessToken and map it to both headers. Parameterize the profile name via an Application Setting so test/prod switch cleanly. Finally, test by enabling DEBUG on the connector to confirm both headers are present and that refresh works on token expiry.