关于Create DMP Segment API响应头中Segment ID对应字段（X-LinkedIn-Id/x-linkedin-id）变更的正式问询

Hey folks,

We’ve been relying on the X-LinkedIn-Id response header field to pull SegmentID values in our legacy codebase for years. Recently, we noticed this header has switched to all lowercase: x-linkedin-id, which completely broke our code’s functionality.

We’re facing a critical decision—whether to roll back our existing code or update it to use the lowercase field—and we need clear answers to these key questions:

• Is this header name change temporary or a permanent breaking update? This will directly dictate our next steps for code adjustments.
• We combed through official documentation but couldn’t find any mention of this change. Can someone share context or details about why this shift happened, to help us finalize our code fixes properly?
• Could we get access to the LinkedIn API’s change log that documents this specific update?

On top of that, we’ve spotted an inconsistency between official resources that’s adding to our confusion:

• The Create DMP Segment documentation uses the all-lowercase x-linkedin-id field
• But LinkedIn’s rest.li protocol repository still references the uppercase X-LinkedIn-Id field

Our code was built using the uppercase field from the rest.li repo, which is exactly why we hit this roadblock when the live API switched to lowercase. Any guidance on resolving this discrepancy would be massively helpful.

Thanks in advance for any insight or help you can offer!

内容的提问来源于stack exchange，提问作者Anurag sinha