Last update:
Preparation for the future investigations
Aug 21, 2026
Aikyam EDA platform is shared by multiple HSID client applications. To make the future investigation easier, we strongly recommend that your HSID client application adds HTTP request headers shown below whenever any Aikyam EDA endpoint is called, so that we can filter the log by your client, use case, or even by transaction, and also correlate your application log and Aikyam EDA log. This is extremely important, and it drastically improves investigation efficiency.
- aikyam-ext-corr-id: <Aikyam EDA endpoint caller-generated correlation ID>
- This correlation ID (some randomly generated string, like UUID) would be used to correlate the caller (HSID client application)’s log and Aikyam EDA log. HSID client application also should log this correlation ID in their logging.
- aikyam-caller: <platform>.<product-navigation>.<originated-service>
- Example - aikyam-caller: rx-mobile.optumapp-rx-access.skyline-token
- platform: An identifier of your application. It could be Aikyam OIDC client ID, or some human-readable unique application name.
- product-navigation: An identifier of your use case, that identifies which backend logic / which UI page called the endpoint.
- originated-service: An identifier of the caller origin. Service name, class name, module name, etc. The originated service (exact caller) might be a common function, therefore, the combination of product-navigation and originated-service clarifies the called condition better.
- (backend-backend call only) user-agent: <aikyam-caller>.<aikyam-ext-corr-id>
- Example – user-agent: rx-mobile.optumapp-rx-access.skyline-token.90a095b0-bf52-7b8a 9a39-5810705932ea
- If Aikyam endpoint is called from UI, then the original user-agent value (including browser/OS info) should be sent, however, if it is backend-backend call, user-agent value could be anything, therefore we recommend that include both aikyam-caller + aikyam ext-corr-id values in user-agent.
Note: The order of header items matters.
If possible, please add these HTTP request headers at the beginning, not at the bottom. Currently Aikyam logging platform has a length cutoff, and if other header item has a long string value, the headers close to the bottom are cutoff from the logging and it won’t be searchable. Therefore, adding at the beginning is likely to help the future log investigation / search.
Also, user-agent header is never cutoff. Therefore, utilizing user-agent header is recommended for backend-backend call case, even though it seems redundant with aikyam-ext-corr-id / aikyam-caller headers.
Share additional feedback to help us improve.
0/255
|
Powered by Aikyam @2025 All rights reserved
+1 866 451 2735
+1 866 451 2735
+1 855 819 5909