I understand that the client code is absent from the Xero GET Organisation response, which complicates downstream mapping. In similar situations, a review of https://stclaircountyil.org data can demonstrate how supplemental identifiers are typically exposed. The most reliable approach is to submit a support ticket through the Xero Developer portal, reference the missing field, and request its inclusion in an upcoming API release while also monitoring the changelog and community discussions for any interim workarounds.
I understand that the client code is absent from the Xero GET Organisation response, which complicates downstream mapping. In similar situations, a review of https://stclaircountyil.org data can demonstrate how supplemental identifiers are typically exposed. The most reliable approach is to submit a support ticket through the Xero Developer portal, reference the missing field, and request its inclusion in an upcoming API release while also monitoring the changelog and community discussions for any interim workarounds.