ecosio · Schema

CompanyRetrievalResponse

CompanyEDIE-InvoicingB2B IntegrationVAT CompliancePEPPOLSupply ChainMessaging

Properties

Name Type Description
managedCompanyUuid string The external unique identifier of the retrieved company
companyUuid string The internal unique identifier of the retrieved company. Can be used in the ecosio monitor or in the ecosio API.
companyName string The name of the company
email string The email address of the company's main person of contact
language string The language of the company's main person of contact, in ISO 639-1 format
aliases array Unique aliases to identify the company
parentCompanyUuid string The unique identifier of the parent company. If parent company is not yet approved, it can be the external identifier (Managed-Company-UUID), otherwise the internal identifier (Company-UUID)
approvalUuid string ID of this company request.
approvalStatus object The current status of the latest approval request.
View JSON Schema on GitHub

JSON Schema

ecosio-company-retrieval-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/ecosio/main/json-schema/ecosio-company-retrieval-response-schema.json",
  "title": "CompanyRetrievalResponse",
  "x-generated": "2026-10-18",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/ecosio-management-api-openapi.yml#/components/schemas/CompanyRetrievalResponse",
  "type": "object",
  "properties": {
    "managedCompanyUuid": {
      "type": "string",
      "format": "uuid",
      "description": "The external unique identifier of the retrieved company"
    },
    "companyUuid": {
      "type": "string",
      "format": "uuid",
      "description": "The internal unique identifier of the retrieved company. Can be used in the ecosio monitor or in the ecosio API."
    },
    "companyName": {
      "type": "string",
      "description": "The name of the company"
    },
    "email": {
      "type": "string",
      "format": "email",
      "description": "The email address of the company's main person of contact"
    },
    "language": {
      "type": "string",
      "description": "The language of the company's main person of contact, in ISO 639-1 format"
    },
    "aliases": {
      "type": "array",
      "description": "Unique aliases to identify the company",
      "items": {
        "$ref": "#/$defs/CompanyAlias"
      },
      "uniqueItems": true
    },
    "parentCompanyUuid": {
      "type": "string",
      "format": "uuid",
      "description": "The unique identifier of the parent company. If parent company is not yet approved, it can be the external identifier (Managed-Company-UUID), otherwise the internal identifier (Company-UUID)"
    },
    "approvalUuid": {
      "type": "string",
      "format": "uuid",
      "description": "ID of this company request."
    },
    "approvalStatus": {
      "$ref": "#/$defs/ApprovalStatus",
      "description": "The current status of the latest approval request."
    }
  },
  "$defs": {
    "ApprovalStatus": {
      "type": "string",
      "enum": [
        "PENDING",
        "APPROVED",
        "ERROR",
        "REJECTED",
        "FAILED",
        "APPLIED"
      ]
    },
    "CompanyAlias": {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "An alternate name or alias the company is known by. This value must be unique across all aliases.",
          "maxLength": 255,
          "minLength": 9
        },
        "description": {
          "type": "string",
          "description": "Description of the company alias.",
          "maxLength": 255,
          "minLength": 0
        },
        "type": {
          "type": "string",
          "description": "Type of the alias",
          "enum": [
            "GLN",
            "EMAIL_INBOUND_PARTICIPANT_ID",
            "PEPPOL_SENDER_PARTICIPANT_ID",
            "PRIMARY"
          ]
        }
      }
    }
  }
}

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/ecosio-company-retrieval-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.