Thomson Reuters · Schema

ApplicationResponse

Response from getDocumentStatusAPI

LegalTaxFinanceRisk ManagementFraud PreventionComplianceData

Properties

Name Type Description
id string id
issueDate string issueDate
sourceSystem string It is the source of payload.
customerType string This field signifies the type of customer we are dealing with in this transaction. Supported values are B2B and B2G. * `B2B` - Business to business * `B2G` - Business to government
senderParty object
receiverParty object
documentResponses array
documentReference object
clearanceResponse object
View JSON Schema on GitHub

JSON Schema

thomson-reuters-application-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/thomson-reuters/main/json-schema/thomson-reuters-application-response-schema.json",
  "title": "ApplicationResponse",
  "description": "Response from getDocumentStatusAPI",
  "x-generated": "2026-10-20",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/thomson-reuters-onesource-einvoice-openapi.yml#/components/schemas/ApplicationResponse",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "pattern": "^(?!\\s*$).+",
      "description": "id"
    },
    "issueDate": {
      "type": "string",
      "description": "issueDate",
      "format": "date"
    },
    "sourceSystem": {
      "type": "string",
      "description": "It is the source of payload."
    },
    "customerType": {
      "type": "string",
      "description": "This field signifies the type of customer we are dealing with in this transaction. Supported values are B2B and B2G.\n  * `B2B` - Business to business\n  * `B2G` - Business to government",
      "enum": [
        "B2B",
        "B2G"
      ]
    },
    "senderParty": {
      "$ref": "#/$defs/PartyResponse"
    },
    "receiverParty": {
      "$ref": "#/$defs/PartyResponse"
    },
    "documentResponses": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/DocumentResponse"
      }
    },
    "documentReference": {
      "$ref": "#/$defs/DocumentReferenceDocumentStatus"
    },
    "clearanceResponse": {
      "$ref": "#/$defs/ClearanceResponse"
    }
  },
  "$defs": {
    "ClearanceResponse": {
      "title": "ClearanceResponse",
      "type": "object",
      "properties": {
        "referenceId": {
          "type": "string"
        },
        "qrString": {
          "type": "string"
        },
        "authorityName": {
          "type": "string"
        }
      }
    },
    "Contact": {
      "title": "Contact",
      "description": "A group of business terms providing contact information",
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "Name of contact person.  One needs to be filled out if the seller contact tag is used"
        },
        "telephone": {
          "type": "string",
          "description": "Phone number of contact person.  One needs to be filled out if the seller contact tag is used"
        },
        "electronicMail": {
          "type": "string",
          "pattern": "^[^=|+\\-@].*",
          "description": "E-mail of contact person."
        }
      }
    },
    "DocumentReferenceDocumentStatus": {
      "title": "DocumentReference",
      "type": "object",
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^(?!\\s*$).+",
          "description": "unique id of DocumentReference"
        },
        "issueDate": {
          "type": "string",
          "description": "issueDate of DocumentReference",
          "format": "date"
        },
        "documentType": {
          "type": "string",
          "description": "type of document type"
        },
        "documentSubType": {
          "type": "string",
          "description": "type of document sub type"
        }
      }
    },
    "DocumentResponse": {
      "type": "object",
      "properties": {
        "responseCode": {
          "type": "string",
          "description": "response code\n  * `ERR` - Error\n  * `INI` - Initiated\n  * `INP` - In progress\n  * `SUC` - Success\n  * `CLA` - Clearance accepted\n  * `CLR` - Clearance rejected\n  * `BRI` - Business response initiated\n  * `BUA` - Business accepted\n  * `BUR` - Business rejected\n  * `CAN` - Cancel\n  * `CCA` - Conditionally accepted\n  * `DDP` - Deadline passed",
          "enum": [
            "ERR",
            "INI",
            "INP",
            "SUC",
            "CLA",
            "CLR",
            "BRI",
            "BUA",
            "BUR",
            "CAN",
            "CCA",
            "DDP"
          ]
        },
        "statuses": {
          "type": "array",
          "items": {
            "$ref": "#/$defs/Status"
          }
        }
      }
    },
    "PartyIdentificationId": {
      "title": "PartyIdentificationId",
      "type": "object",
      "required": [
        "value",
        "schemeId"
      ],
      "properties": {
        "value": {
          "type": "string",
          "pattern": "^[^=|+\\-@].*",
          "description": "unique id for party"
        },
        "schemeId": {
          "type": "string",
          "description": "scheme id for party\n  * `MY:TIN`\n  * `MY:TTX`\n  * `MY:NRIC`\n  * `MY:BRN`\n  * `MY:PASSPORT`\n  * `MY:ARMY`\n  * `ZZZ` - Non mandatory scenario\n  * `0002` - System Information et Repertoire des Entreprise et des Etablissements: SIRENE: Notes on Use of Code: The Sirene number is used in France mainly for the official registration in the Trade Register and as the only number used between authorities and organizations, and between authorities when dealing with data interchange on organizations. Issuing agency: Institut National de la Statistique et des Etudes Economiques, (I.N.S.E.E.), France.\n  * `0003` - Codification Numerique des Etablissments Financiers En Belgique: Notes on Use of Code: Many financial institutions have more than one code number, e.g. to indicate each branch individually. The codes can be reallocated over the time (mostly in the case where a financial institution terminates its activity). Some code numbers are currently unused. Code numbers 990 through 999 are reserved. Issuing agency: Association Belge des Banques, Belgium.\n  * `0004` - NBS/OSI NETWORK: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing and naming tree as depicted in Addendum 2 to ISO 8348. Issuing agency: National Bureau of Standards, USA.\n  * `0005` - USA FED GOV OSI NETWORK: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing and naming tree as depicted in Addendum 2 to ISO 8348. Issuing agency: National Bureau of Standards, USA.\n  * `0006` - USA DOD OSI NETWORK: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing and naming tree as depicted in Addendum 2 to ISO 8348. Issuing agency: Defense Communication Agency, USA.\n  * `0007` - Organisationsnummer: Notes on Use of Code: The third digit in the organisation number is never lower than 2 in order to avoid it being confused with personal numbers. Issuing agency: The National Tax Board, SWEDEN.\n  * `0008` - LE NUMERO NATIONAL: Issuing agency: Ministere De L'interieur et de la Fonction Publique, Belgium.\n  * `0009` - SIRET-CODE: Issuing agency: DU PONT DE NEMOURS (FRANCE) S.A. France.\n  * `0010` - Organizational Identifiers for Structured Names under ISO 9541 Part 2: Notes on Use of Code: The organizational codes established under this coding systems constitute the registered organizational identifiers recognised under ISO 9541-2. That standard effectively establishes agreements under which, as allowed by clauses 5.1 and 5.3 of ISO 6523, both the ICD and the organization name are generally omitted, from the SIO, and thus only the organization code portion of the SIO is interchanged. Issuing agency: Association for Font Information Interchange, USA.\n  * `0011` - International Code Designator for the Identification of OSI-based, Amateur Radio\n              Organizations, Network Objects and Application Services.: Notes on Use of Code: Specific object and attribute naming conventions are currently being defined. Issuing agency: The Radio Amateur Telecommunications Society, USA.\n  * `0012` - European Computer Manufacturers Association: ECMA: Issuing agency: European Computer Manufacturers Association, SWITZERLAND.\n  * `0013` - VSA FTP CODE (FTP = File Transfer Protocol): Notes on Use of Code: The code serves the addressing between the communicating partners. Issuing agency: Verband der Automobilindustrie e.V., GERMANY.\n  * `0014` - NIST/OSI Implememts' Workshop: Notes on Use of Code: The ICD code forms the initial part of the Workshop naming and addressing tree. Issuing agency: United States Department of Commerce, National Institute of Standards and Technology, Gaithersburg, USA.\n  * `0015` - Electronic Data Interchange: EDI: Issuing agency: Avon Rubber p.l.c. UK.\n  * `0016` - EWOS Object Identifiers: Notes on Use of Code: a) In the SIO the Organization Name will normally be omitted, b) The code is primarily intended for the registration of Objects Identifiers according to ISO 8824: Level 1: iso (1), Level 2: identified-organization (3), Level 3: ewos (0016), Level 4: and higher: (defined by EWOS conventions) Issuing agency: EWOS (European Workshop for Open Systems), BELGIUM.\n  * `0017` - COMMON LANGUAGE: Notes on Use of Code: Codes for named populated places, geographic places, geopolitical places, outlaying areas, and other related entities of the state of the United States, provinces and territories of Canada, countries of the world, and other, unique areas. Also for the identification of organizations, places, equipment and governmental entities by the telecommunication industry. Issuing agency: Data Communications Technology Planning, USA.\n  * `0018` - SNA/OSI Network: Notes on Use of Code: The ICD code will also form the initial part of the OSI Network addressing and naming tree as depicted in Addendum 2 to ISO 8348. Issuing agency: International Business Machines Corporation, USA.\n  * `0019` - Air Transport Industry Services Communications Network: The ICD code forms the initial part of the OSI network addressing and naming tree as depicted in Addendum 2 to ISO 8348. Issuing agency: International Air Transport Association, Switzerland.\n  * `0020` - European Laboratory for Particle Physics: CERN: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing and naming tree as depicted in Addendum 2 of ISO 8348. Issuing agency: European Laboratory for Particle Physics, Switzerland.\n  * `0021` - SOCIETY FOR WORLDWIDE INTERBANK FINANCIAL, TELECOMMUNICATION S.W.I.F.T.: Notes on Use of Code: To be used for assignment of object identifiers (ISO 8824/8825) Issuing agency: SOCIETY FOR WORLDWIDE INTERBANK FINANCIAL, TELECOMMUNICATION S.W.I.F.T. BELGIUM.\n  * `0022` - OSF Distributed Computing Object Identification: Notes on Use of Code: OSF provides public domain software in OS, ISO networking and management. The initial use of the coding system are for identifying the following objects in OSF's distributed computing environment: the attributes of entries in the distributed directory, the object class of each entry in the directory, the type of name components (RDNs), the communication protocol profiles, the interfaces offered by. Issuing agency: Open Software Foundation, USA.\n  * `0023` - Nordic University and Research Network: NORDUnet: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing and tree as depicted in Addendum 2 of ISO 8348. Issuing agency: NORDUnet, c/o SICS, Sweden.\n  * `0024` - Digital Equipment Corporation: DEC: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing as described in ISO8348 Addendum 2. Issuing agency: Digital Equipment (Europe) S.A.R.L. France.\n  * `0025` - OSI ASIA-OCEANIA WORKSHOP: Notes on Use of Code: The code is used as an element of object identifiers which need to be assigned relating the ISPs (International Standardized Profiles) that AOW is working on. Issuing agency: OSI ASIA-OCEANIA WORKSHOP, JAPAN.\n  * `0026` - NATO ISO 6523 ICDE coding scheme: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing and naming tree depicted in Addendum 2 of ISO 8348. Issuing agency: North Atlantic Treaty Organisation (NATO), Belgium.\n  * `0027` - Aeronautical Telecommunications Network (ATN): Notes on Use of Code: The ICD code forms the initial part of the ISO network addressing and naming tree as depicted in Addendum No 2 to ISO 8348 Issuing agency: International Civil Aviation Organization (ICAO), CANADA.\n  * `0028` - International Standard ISO 6523: Issuing agency: Styria Federn GmbH, AUSTRIA.\n  * `0029` - The All-Union Classifier of Enterprises and Organisations: Issuing agency: General Computing Centre of the State, Committee of the USSR on Statistics, U S S R.\n  * `0030` - AT&T/OSI Network: Notes on Use of Code: The ICD code will also form the Initial Domain Part of the OSI network, addressing and naming tree as specified in Addendum 2 to ISO 8348. Issuing agency: AT&T, Standards and Regulatory Support, UNITED STATES OF AMERICA.\n  * `0031` - EDI Partner Identification Code: Notes on Use of Code: To identify EDI partners. Issuing agency: Odette NL, The Netherlands.\n  * `0032` - Telecom Australia: Notes on Use of Code: The code is used as an element of Object Identifier when defining objects within Telecom Australia. In addition the code shall be used as an element of NSAP addressing. Issuing agency: Australia Telecommunications Corporation, AUSTRALIA.\n  * `0033` - S G W OSI Internetwork: Notes on Use of Code: Exclusive use by S G W .Issuing agency: S G Warburg Group Management Ltd, UK.\n  * `0034` - Reuter Open Address Standard: Notes on Use of Code: To be used in the formation of OSI Network Service Access Point (NSAP) addresses. Issuing agency: Reuters Ltd, UK.\n  * `0035` - ISO 6523 - ICD: Notes on Use of Code: This code will be used internationally by BP thus a non-geographic code is requested. Issuing agency: The British Petroleum Co Plc, UK.\n  * `0036` - TeleTrust Object Identifiers: Notes on Use of Code: a) In the SIO the Organization name will normally be omitted. b) The code is primarily intended for the registration of Object Identifiers for security related objects according to ISO/IEC 8824, Level 1: iso(1), Level 2: identified-organization(3), Level 3: teletrust(0036), Level 4 and higher: (defined by TeleTrust conventions) Issuing agency: TeleTrust Deutschland e.V., GERMANY.\n  * `0037` - LY-tunnus: Notes on Use of Code: It is possible to add 0-4 characters set to the code for more detailed use ofone organization. Characters are digits or capital letter. Issuing agency: National Board of Taxes, FINLAND.\n  * `0038` - The Australian GOSIP Network: Notes on Use of Code: As noted above it will be used as the initial identifier of an NSAP codingscheme. Issuing agency: Standards Australia.\n  * `0039` - The OZ DOD OSI Network: The ICD code forms the initial part of the OSI naming and addressing, tree as depicted in ISO 8348/Add 2 standard. Format of the tree is described in the Australian GOSIP Manuals and used globally. Issuing agency: The Australian Department of Defence, AUSTRALIA.\n  * `0040` - Unilever Group Companies: Notes on Use of Code: To be used in data communications to form part of the Network Address as defined in ISO 8348. The ISO 6523, ICD IDI format with Binary syntax will be used. Issuing agency: Information Technology Group, Unilever Plc, UK.\n  * `0041` - Citicorp Global Information Network: Notes on Use of Code: The ICD code will also form the initial part of the Citicorp Network addressing object identifier tree and naming tree as depicted in Addendum 2 to ISO 8348. Issuing agency: Citicorp Global Information Network, USA.\n  * `0042` - DBP Telekom Object Identifiers: Notes on Use of Code: 1) The ICD is primarily intended for the registration of Object Identifiers, according to ISO 8824/8825 (ANS.1) to be used for the identification resp. registration of: - application layer protocols, - file & document formats, - information objects, - local/remote procedures. The OID structure and the inclusion of the ICD therein is given below: level 1: iso(1), level 2: identifiedOrganisation(3), level 3 (ICD): dbpt(0042), level 4 to n: (defined by Telekom). Issuing agency: DBP Telekom, GERMANY.\n  * `0043` - HydroNETT: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing as depicted in ISO 8348/AD2. Issuing agency: Norsk Hydro a.s., Norway.\n  * `0044` - Thai Industrial Standards Institute (TISI): Notes on Use of Code: The ICD code forms the initial part of international addressing for Thailand. Issuing agency: Thai Industrial Standards Institute (TISI), THAILAND.\n  * `0045` - ICI Company Identification System: Notes on Use of Code: The ICD code will be used to manage NSAP allocation for all ICI companies on a worldwide basis. The organisation code is used Worldwide by ICI application systems to identify ICI registered companies in machine to machine communications. Issuing agency: ICI PLC, UK.\n  * `0046` - FUNLOC: Notes on Use of Code: Current applications are Philips accounting and logistic systems; new application is the identification of objects in the open network environment according to ISO 8824 which starts with a party identification Issuing agency: Royal Philips Electronics N.V., The Netherlands.\n  * `0047` - BULL ODI/DSA/UNIX Network: Notes on Use of Code: To be used in data communications to form part of the network address. The ISO 6523 ICD IDI format with binary syntax will be used. Issuing agency: BULL S.A. FRANCE.\n  * `0048` - OSINZ: Notes on Use of Code: ISO 6523 ICD IDI format with binary syntax will be used. Issuing agency: OSINZ, New Zealand.\n  * `0049` - Auckland Area Health: Notes on Use of Code: ISO 6523 ICD IDI format with binary syntax will be used Issuing agency: Auckland Area Health Board, Information Systems, Greenlane/National Women's Hospital, New Zealand.\n  * `0050` - Firmenich: Notes on Use of Code: Interconnect the plants by an OSI network essentially over X.25 carrier. Issuing agency: Firmenich S A, Switzerland.\n  * `0051` - AGFA-DIS: Notes on Use of Code: Medical Communication Issuing agency: AGFA N.V. BELGIUM.\n  * `0052` - Society of Motion Picture and Television Engineers (SMPTE): Notes on Use of Code: The ICD code will also be used to identify SMPTE constituent organizations (committees, working groups, task forces, etc./), and the objects they, define. The ICD code will also form the Initial Domain Part of the OSI network addressing and naming tree as specified in Addendum 2 tot ISO 8348 Issuing agency: Society of Motion Picture and Television Engineers (SMPTE), USA.\n  * `0053` - Migros_Network M_NETOPZ: Issuing agency: Migros-Genossenschafts-Bund, Switzerland.\n  * `0054` - ISO6523 - ICDPCR: Notes on Use of Code: This code could be used internationally by Pfizer thus a non-geographic code is required. The code forms the initial part of the OSI network addressing and naming tree depicted in Addendum 2 of ISO 8348. Issuing agency: Pfizer Central Research, UK.\n  * `0055` - Energy Net: Issuing agency: ABB Asea Brown Boveri Ltd, Switzerland.\n  * `0056` - Nokia Object Identifiers (NOI): Notes on Use of Code: a) In the SIO the organization name will normally be omitted, b) The code is primarily intended for the registration of Object Identifiers according to ISO/IEC 8824: Level 1:iso(1), Level 2:identified-organization(3), Level 3:nokia(xxxx), Level 4 and higher:defined by Nokia conventions Issuing agency: Nokia Corporation, FINLAND.\n  * `0057` - Saint Gobain: Notes on Use of Code: To be used for assignment of: N.E.T (ISO 8348/Add 2), A.E.T (FTAM, X.400 Psaps, and so on), and object identification (ISO 8824/8825) Issuing agency: Saint Gobain, France.\n  * `0058` - Siemens Corporate Network: Notes on Use of Code: The ICD code will form the initial part of the OSI Network addressing and naming tree as depicted in Addendum 2 to ISO 8348 (Network layer addressing). These addresses will uniquely identify systems within SCN and to the outside world. Issuing agency: Siemens AG, Germany.\n  * `0059` - DANZNET: Issuing agency: DANZAS AG, Switzerland.\n  * `0060` - Data Universal Numbering System (D-U-N-S Number): Notes on Use of Code: The D-U-N-S Number originated to facilitate the compilation of financial status reports on those involved in business transactions but it is now widely used for other purposes also. The number has world wide recognition as a means of identifying businesses and institutions. Issuing agency: Dun and Bradstreet Ltd, UK.\n  * `0061` - SOFFEX OSI: Notes on Use of Code: This code is to assist in uniquely identifying data network node addresses in an international supporting network for financial applications. This supporting network may have operational interfaces to other (private) data networks. Issuing agency: SOFFEX Swiss Options and Financial Futures Exchange AG. Switzerland.\n  * `0062` - KPN OVN: Notes on Use of Code: This code is used in the VTOA network of KPN OVN. Issuing agency: Koninklijke KPN, The Netherlands.\n  * `0063` - ascomOSINet: Issuing agency: Ascom AG, Switzerland.\n  * `0064` - UTC: Uniforme Transport Code: Notes on Use of Code: The code identifies an individual transport or handling unit (e.g. pallet, parcel) for reasons of tracing or tracing. The unit may have an international destination. Issuing agency: Foundation UTC, The Netherlands.\n  * `0065` - SOLVAY OSI CODING: Notes on Use of Code: Whenever possible, ISO 8348 addresses using this code will comply with FIPS PUB 146, with an End System ID of exactly 4 octets, so that the DSP can also conform to ECMA 117 where ECMA's subnet-address maps onto FIPS's Subnet ID concatenated with the End System ID. Issuing agency: Direction Centrale Technique (Informatique Scientifique), Belgium.\n  * `0066` - Roche Corporate Network: Notes on Use of Code: Will be used internationaly by Roche thus a non-geographic code is required. Issuing agency: F. HOFFMANN - LA ROCHE AG, Switzerland.\n  * `0067` - ZellwegerOSINet: Notes on Use of Code: BAKOM - Switzerland. Issuing agency: Zellweger Uster AG, Switzerland.\n  * `0068` - Intel Corporation OSI: Notes on Use of Code: The ICD code will be used to form the Initial Domain Identifier (IDI) portion of the Initial Domain Part (IDP) as described in ISO 8348 Addendum 2 for OSI NSAP addressing. Issuing agency: Intel Corporation, USA.\n  * `0069` - SITA Object Identifier Tree: Notes on Use of Code: SITA intends to use its OID Tree to define its own Objects for use with its OSI-based services (e.g. MHS & OSI Management). Issuing agency: SITA, France.\n  * `0070` - DaimlerChrysler Corporate Network: Notes on Use of Code: The ICD code will form the initial part of the OSI Network addressing and naming free as depicted in Addendum 2 to ISO 8348 (Network Layer addressing). These addresses will uniquely identify systems within DBCN and to the outside world. Issuing agency: DaimlerChrysler AG, GERMANY.\n  * `0071` - LEGO /OSI NETWORK: Notes on Use of Code: The ICD code will also form the Initial Domain Part of the OSI network addressing and naming tree as specified in addendum 2 to ISO 8348. Issuing agency: LEGO Systems Inc, USA.\n  * `0072` - NAVISTAR/OSI Network: Notes on Use of Code: The ICD code will also form the Initial Domain Part of the OSI Network addressing and naming tree as specified in Addendum 2 to ISO 8348. Issuing agency: International Truck & Engine Corp, USA.\n  * `0073` - ICD Formatted ATM address: Notes on Use of Code: Used as an ATM address prefix by, 1) Newbridge ATM terminal equipment: a) when performing user - network address registration, b) transparently initiating signalled ATM connections on behalf of other non-ATM (LAN) devices, c) directly initiating signalled ATM connections, 2) Newbridge ATM switching equipment used to: a) perform network - user address registration, b) perform routing of Switched Virtual Connections across a private ATM cell switching network. Issuing agency: Newbridge Networks Corporation, CANADA.\n  * `0074` - ARINC: Notes on Use of Code: ARINC will define its own Objects for use with its OSI-based systems and services. ARINC will also define Objects for use within the Aeronautical industry. Issuing agency: ARINC Incorporated, USA.\n  * `0075` - Alcanet/Alcatel-Alsthom Corporate Network: Notes on Use of Code: The ICD code forms the initial part of the OSI network addressing scheme as depicted in Addendum 2 of ISO 8384. Issuing agency: Alcatel Network Services Deutschland GmbH, GERMANY.\n  * `0076` - Sistema Italiano di Identificazione di ogetti gestito da UNINFO: Notes on Use of Code: To be used for assignments of object identifiers according to ISO 8824 and ISO 8825. Issuing agency: UNINFO, ITALY.\n  * `0077` - Sistema Italiano di Indirizzamento di Reti OSI Gestito da UNINFO: Notes on Use of Code: The ICD code forms the initial part of the OSI network Addressing and naming tree depicted in Addendum 2 of ISO 8348. Issuing agency: UNINFO, ITALY.\n  * `0078` - Mitel terminal or switching equipment: Notes on Use of Code: The ICD code will form the initial part of the naming tree for: 1 - Private Integrated Services Network manufacturer-specific information as the Organization identifier forming the initial part of the OBJECT IDENTIFIER tree. 2 - OSI Application Layer such as CSTA (ECMA 179). Issuing agency: Mitel Corporation, Canada.\n  * `0079` - ATM Forum: Notes on Use of Code: The ICD code will also form part of the Initial Domain Part of the OSI network addressing as specified in Addendum 2 to ISO 8348. Issuing agency: The ATM Forum, USA.\n  * `0080` - UK National Health Service Scheme, (EDIRA compliant): Notes on Use of Code: EDIRA recommendations for coding in EDIFACT and other EDI systems. Issuing agency: National Health Service, UK.\n  * `0081` - International NSAP: Issuing agency: Federal Office for Communications, Switzerland.\n  * `0082` - Norwegian Telecommunications Authority's, NTA'S, EDI, identifier scheme (EDIRA\n              compliant): Notes on Use of Code: For use in EDIFACT messages in accordance with current national recommendation on identification of EDI objects. (EDIRA compliant). Issuing agency: Norwegian Telecommunications Authority, NORWAY.\n  * `0083` - Advanced Telecommunications Modules Limited, Corporate Network: Notes on Use of Code: The ICD code will also form part of the Initial Domain Part of the OSI network addressing as specified in Addendum 2 to ISO 8348. Issuing agency: ATM Ltd, ENGLAND.\n  * `0084` - Athens Chamber of Commerce & Industry Scheme (EDIRA compliant): Notes on Use of Code : EDIRA recommendations for coding in EDIFACT and other EDI syntaxes. Issuing agency: Athens Chamber of Commerce & Industry, Greece.\n  * `0085` - Swiss Chambers of Commerce Scheme (EDIRA) compliant: Intended Purpose/App. Area Numerical identifiers of organizations. Issuing agency: Zurich Chamber of Commerce on behalf of Swiss Chambers, of Commerce, Switzerland.\n  * `0086` - United States Council for International Business (USCIB) Scheme, (EDIRA compliant): EDIRA recommendations for coding in EDIFACT and other EDI syntaxes. Issuing agency: United States Council for Internationa Business (USCIB), 1212 Avenue of the Americas, USA.\n  * `0087` - National Federation of Chambers of Commerce & Industry of Belgium, Scheme (EDIRA compliant): Issuing agency: National Federartion of Chambers of Commerce & Industry of, Belgium, Belgium.\n  * `0088` - EAN Location Code: Issuing agency: EAN International, Belgium.\n  * `0089` - The Association of British Chambers of Commerce Ltd. Scheme, (EDIRA compliant): Issuing agency: The Association of British Chambers of Commerce Ltd., UK.\n  * `0090` - Internet IP addressing - ISO 6523 ICD encoding: Issuing agency: Internet Assigned Numbers Authority, USA.\n  * `0091` - Cisco Sysytems / OSI Network: Issuing agency: Cisco Systems, USA.\n  * `0093` - Revenue Canada Business Number Registration (EDIRA compliant): Issuing agency: Revenue Canada, CANADA.\n  * `0094` - DEUTSCHER INDUSTRIE- UND HANDELSTAG (DIHT) Scheme (EDIRA compliant): Issuing agency: Deutscher Industrie -und Handelstag (DIHT), Germany.\n  * `0095` - Hewlett - Packard Company Internal AM Network: Issuing agency: Hewlett - Packard Company, USA.\n  * `0096` - DANISH CHAMBER OF COMMERCE Scheme (EDIRA compliant): Issuing agency: Danish Chamber of Commerce, Denmark.\n  * `0097` - FTI - Ediforum Italia, (EDIRA compliant): Issuing agency: FTI - Ediforum Italia, ITALY.\n  * `0098` - CHAMBER OF COMMERCE TEL AVIV-JAFFA Scheme (EDIRA compliant): Issuing agency: Chamber of Commerce Tel Aviv-Jaffa, ISRAEL.\n  * `0099` - Siemens Supervisory Systems Network: Issuing agency: Siemens AG, Germany.\n  * `0100` - PNG_ICD Scheme: Issuing agency: GPT Limited, UK.\n  * `0101` - South African Code Allocation: Issuing agency: Thawte Consulting, 33 Protea Way, Durbanville 7550, South Africa\n  * `0102` - HEAG: Issuing agency: Hessische Elektrizitats-AG, Germany.\n  * `0104` - BT - ICD Coding System: Issuing agency: Tony Holmes, UK.\n  * `0105` - Portuguese Chamber of Commerce and Industry Scheme (EDIRA compliant): Issuing agency: Portuguese Chamber of Commerce and Industry, Portugal.\n  * `0106` - Vereniging van Kamers van Koophandel en Fabrieken in Nederland (Association of Chambers of Commerce and Industry in the Netherlands), Scheme (EDIRA compliant): Issuing agency: Vereniging van Kamers van Koophandel en Fabrieken in Nederland Watermolenlaan, The Netherlands.\n  * `0107` - Association of Swedish Chambers of Commerce and Industry Scheme (EDIRA compliant): Issuing agency: Association of Swedish Chambers of Commerce and Industry, Sweden.\n  * `0108` - Australian Chambers of Commerce and Industry Scheme (EDIRA compliant): Issuing agency: Australian Chambers of Commerce and Industry, Australia.\n  * `0109` - BellSouth ICD AESA (ATM End System Address): Issuing agency: BellSouth Corporation, USA.\n  * `0110` - Bell Atlantic: Issuing agency: Bell Atlantic, USA.\n  * `0111` - Object Identifiers: Issuing agency: Institute of Electrical and Electronics Engineers, USA.\n  * `0112` - ISO register for Standards producing Organizations: Issuing agency: International Organization for Standardization (ISO), SWITZERLAND.\n  * `0113` - OriginNet: Issuing agency: Origin BV, The Netherlands.\n  * `0114` - Check Point Software Technologies: Issuing agency: Check Point Software Technologies Ltd, ISRAEL.\n  * `0115` - Pacific Bell Data Communications Network: Issuing agency: Pacific Bell, USA.\n  * `0116` - PSS Object Identifiers: Issuing agency: PSS (Postal Security Services), FINLAND.\n  * `0117` - STENTOR-ICD CODING SYSTEM: Issuing agency: Stentor Resource Centre Inc., Canada.\n  * `0118` - ATM-Network ZN'96: Issuing agency: Deutsche Telekom AG, Germany.\n  * `0119` - MCI / OSI Network: Issuing agency: MCI Telecommunications Corporation, Technical Standards Management, USA.\n  * `0120` - Advantis: Issuing agency: Advantis, USA.\n  * `0121` - Affable Software Data Interchange Codes: Issuing agency: Affable Software Corporation, Canada.\n  * `0122` - BB-DATA GmbH: Issuing agency: BB-DATA GmbH, Germany.\n  * `0123` - BASF Company ATM-Network: Issuing agency: BASF Computer Services GmbH, Germany.\n  * `0124` - IOTA Identifiers for Organizations for Telecommunications Addressing using the ICD system format defined in ISO/IEC 8348: Issuing agency: DISC, British Standards Institution, UK.\n  * `0125` - Henkel Corporate Network (H-Net): Issuing agency: Henkel KgaA, Germany.\n  * `0126` - GTE/OSI Network: Issuing agency: GTE, Industry Standards, USA.\n  * `0127` - Dresdner Bank Corporate Network: Issuing agency: Dresdner Bank AG, Germany.\n  * `0128` - BCNR (Swiss Clearing Bank Number): Issuing agency: Telekurs AG, Switzerland.\n  * `0129` - BPI (Swiss Business Partner Identification) code: Issuing agency: Telekurs AG, Switzerland.\n  * `0130` - Directorates of the European Commission: Issuing agency: European Commission, Belgium\n  * `0131` - Code for the Identification of National Organizations: Issuing agency: China National Organization Code Registration Authority, P.R. of China.\n  * `0132` - Certicom Object Identifiers: Issuing agency: Certicom Corp, U.S.A.\n  * `0133` - TC68 OID: Issuing agency: ISO TC68, Banking and Related Financial Services, USA.\n  * `0134` - Infonet Services Corporation: Issuing agency: Infonet NV/SA, Belgium.\n  * `0135` - SIA Object Identifiers: Issuing agency: SIA-Società Interbancaria per l'Automazione S.p.A., ITALIA.\n  * `0136` - Cable & Wireless Global ATM End-System Address Plan: Issuing agency: Cable & Wireless Global Business Inc., USA\n  * `0137` - Global AESA scheme: Construct and Administer AESAs, Routing of ATM switched connections Use to from globally unique Global One ICD AESAs. Issuing agency: Global One, Belgium.\n  * `0138` - France Telecom ATM End System Address Plan: The coding system will be used to provide ATM End System Addresses based on ICD format NSAP addresses. These addresses will be used to uniquely identify U

# --- truncated at 32 KB (81 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/thomson-reuters/refs/heads/main/json-schema/thomson-reuters-application-response-schema.json

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/thomson-reuters-application-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.