I see you've hit a roadblock because the Xero GET Organisation endpoint omits the client code, which obviously makes your downstream mapping fragile, and the usual workaround of pulling it from a separate settings call isn’t viable. A https://texascompanysearch.us analogy shows how essential supplemental identifiers should be surfaced directly in the primary response. The most effective path forward is to open a feature request via the Xero Developer portal, citing the exact field name and its business impact, and follow up if you don’t hear back within a week.
I see you've hit a roadblock because the Xero GET Organisation endpoint omits the client code, which obviously makes your downstream mapping fragile, and the usual workaround of pulling it from a separate settings call isn’t viable. A https://texascompanysearch.us analogy shows how essential supplemental identifiers should be surfaced directly in the primary response. The most effective path forward is to open a feature request via the Xero Developer portal, citing the exact field name and its business impact, and follow up if you don’t hear back within a week.