> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/use-cases/ultimate-parent/output-the-json-payload-field-by-field.md). # Output — the JSON payload, field by field This technical reference guide provides an exhaustive breakdown of the JSON payload returned by every Delpha Ultimate Parent resolution — via API, MCP, or Salesforce. In Salesforce, the payload is stored in the D Ultimate Data (`delpha__DDQ_QualityUltimateRecommendedData__c`) field, and the headline values land in the fields documented in [What are the Delpha Ultimate Parent Fields](/delpha-for-salesforce/how-to-faq/delpha-ultimate-parents/what-are-the-delpha-ultimate-parent-fields.md). It is designed for developers, Salesforce Administrators, and Data Stewards who need to audit or programmatically parse Delpha's corporate hierarchy data. ## Technical Breakdown: The Ultimate Parent JSON Payload The payload is a comprehensive audit trail and intelligence record. It details the exact algorithmic logic, legal entity identifiers (LEIs), financial data sourcing, and validation protocols used to determine the corporate hierarchy. The payload contains two main root objects: `recommendations` and `common`. ### 1. The `recommendations` Array This block contains the final recommendation generated by the analysis. * `account_name` *(String)*: The clean, verified commercial name of the recommended parent company. * `account_id` *(String/Null)*: The 18-character Salesforce Account ID if the record already exists in your CRM. If `null`, Delpha has identified the entity externally, meaning a new Account record may need to be created or matched. * `status` *(String)*: The life-cycle status of this suggestion (e.g., `Potential`, `Accepted`, `Rejected`). * `score` *(Integer)*: The overall confidence level of this specific recommendation node on a scale of 0 to 100. * `sources` *(Array)*: An audit trail of the evaluations that contributed to this recommendation. * `timestamp`: The exact date and time the evaluation occurred. * `score`: The confidence score given during that specific assessment runner. * `source`: The engine or module that triggered the run (e.g., `Assessment`). ### 2. The Core Verification Engine (`common`) The `common` block houses the structural data, corporate metadata, and strict audit tracks used to validate the hierarchy. #### **Section A: Evidence & Evaluation Protocols** These fields detail the precise logic engine and regulatory frameworks used to audit the company. * `evidence_summary` *(String)*: A highly dense, structured summary of the verification steps executed by Delpha. It breaks down into five core pillars: * *Identity*: Confirms the matching and legal verification of the local entity (e.g., matching the local name to its legal registration name). * *Chain*: Maps the exact structural pathway from the local subsidiary up to the suggested global node. * [*Protocol*](/use-cases/ultimate-parent/how-selection-works/how-delpha-selects-the-ultimate-parent-the-10-logic-protocols.md): The specific financial logic protocol used to evaluate the hierarchy rules (e.g., `Protocol 9 (Active Conglomerate)` handles complex global public groups with specific shareholder thresholds). * *Discard Check*: Details if any intermediate holding companies or defunct entities were intentionally skipped or flagged during analysis. * *GTM Selection*: The final Go-To-Market business rule explaining why this node is selected (e.g., treating a widely held public company as a terminal node because no single shareholder holds >50% control). * `comment` *(String)*: The detailed narrative explaining the corporate legal reality of the entity chain (e.g., outlining buyouts of minority shares, country of origin adjustments, and specific shareholder control mechanics). * `ultimate_parent_source_level` *(String)*: The authoritative compliance tier from which the corporate structure was extracted (e.g., `Securities Filing`, `Regulatory Registry`). * `source_url` *(String)*: The direct digital location or investor relations source where the structural data was officially verified. #### **Section B: Institutional Data & Financial Identifiers** * `ultimate_parent_legal_name` *(String)*: The exact, un-truncated legal registration name of the final parent company. * `ultimate_parent_commercial_name` *(String)*: The recognized trading or brand name of the ultimate parent. * `ultimate_parent_website` *(String)*: The validated corporate homepage URL for the top-tier entity. * `ultimate_parent_website_validated` *(Boolean)*: A system flag verifying that the parent website is active, reachable, and correctly aligned with the entity. * `ultimate_parent_country` *(String)*: The 2-letter ISO country code where the ultimate parent is legally headquartered (e.g., `LU` for Luxembourg). * `relationship_type` *(String)*: How the Target relates to the selected Ultimate Parent. One of `Wholly Owned`, `Joint Venture`, `Member Firm/Franchise`, `Portfolio Company`, `Brand/Division`, `Independent`. * `subsidiary_commercial_name` *(String)*: The commercial/brand name of the input record being analyzed. * `is_self_ultimate` *(Boolean)*: Set to `true` if the current record is its own global ultimate parent; `false` if it answers to a higher corporate authority. #### **Section C: Processing Logs & Operational Metadata** * `confidence` *(Float)*: The normalized confidence score behind the recommendation, ranging from `0.0` to `1.0`. * `input_data_error` *(Boolean)*: A health check flag indicating if the original data provided from Salesforce contained critical errors preventing a clean search. * `data_error_details` *(String)*: Log notes detailing what failed if `input_data_error` is triggered. ### 3. The `ownership_chain` Blueprint The `ownership_chain` parameter contains a serialized JSON array representing the actual corporate ladder, node by node, from bottom to top. Each node object in this chain contains deep-level compliance markers: * `entity_legal_name` & `entity_commercial_name`: The official legal vs. operational brand name of that specific tier. * `entity_type`: The legal classification of the business structure (e.g., `Corporation`). * `entity_country` & `entity_website`: Regional tracking and validated web footprint for that specific tier. * `ownership_status`: The legal status of this tier's stake in the company below it (e.g., `Majority/Controlling`, `Equal/Joint`, `Unknown`). * `is_ultimate_financial_parent`: A critical flag pointing directly to the final node in the financial data graph (`true` or `false`). * `is_discarded`: A boolean flag indicating whether this node was bypassed in favor of a cleaner operational target. * `entity_lei_data` *(Object)*: Contains institutional-grade data pulled directly from global financial oversight bodies (such as GLEIF): * `lei_number`: The official 20-character Global Legal Entity Identifier. * `legal_id`: The local country tax/corporate registration number (e.g., Brazil's CNPJ format). * `lei_source`: The validation registry lookup URL. * `legal_jurisdiction`: The legal jurisdiction governing the entity. * `headquarters_address`: The comprehensive physical corporate headquarters tracking block (`country`, `city`, `postalCode`, `addressLines`, `region`). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.delpha.io/use-cases/ultimate-parent/output-the-json-payload-field-by-field.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.