beel-es · Schema

ListCompanyStats200Response

InvoicingSpainFintechSoftware-as-a-Service

Properties

Name Type Description
success boolean
data object
meta object
View JSON Schema on GitHub

JSON Schema

beel-es-list-company-stats200-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/beel-es/json-schema/beel-es-list-company-stats200-response-schema.json",
  "title": "ListCompanyStats200Response",
  "x-generated": "2026-11-10",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/beel-es-accountcompanies-api-openapi.yml#/components/schemas/ListCompanyStats200Response",
  "type": "object",
  "properties": {
    "success": {
      "type": "boolean"
    },
    "data": {
      "type": "object",
      "required": [
        "stats",
        "pagination"
      ],
      "properties": {
        "stats": {
          "type": "array",
          "items": {
            "$ref": "#/$defs/CompanyStatsData"
          }
        },
        "pagination": {
          "$ref": "#/$defs/Pagination"
        }
      }
    },
    "meta": {
      "$ref": "#/$defs/ResponseMeta"
    }
  },
  "$defs": {
    "CompanyStatsData": {
      "type": "object",
      "required": [
        "company_id",
        "invoice_count"
      ],
      "properties": {
        "company_id": {
          "type": "string",
          "format": "uuid"
        },
        "invoice_count": {
          "type": "integer",
          "format": "int64",
          "description": "Fiscal documents issued by this company. Drafts, scheduled invoices and proformas never count, because there is no fiscal document yet. A rectifying invoice counts as a document of its own. An invoice voided with `POST /v1/companies/{company_id}/invoices/{invoice_id}/void` (issued by mistake) or a simplified invoice replaced by a standard invoice does not count, and neither does a rectifying invoice of an invoice voided that way. An invoice voided by a total rectifying invoice keeps counting, together with that rectifying invoice, so the pair counts as two documents.\nNot monotonic: voiding an invoice with that endpoint lowers this count, and rectifying an invoice for its full amount raises it by one document. Do not use it as a synchronisation cursor; webhooks and `GET /v1/accounts/{account_id}/request-logs` are the surfaces for that."
        },
        "last_invoice_at": {
          "type": [
            "string",
            "null"
          ],
          "format": "date-time",
          "description": "Issue date of the most recent document in the same set as `invoice_count` (ISO 8601), or null if none. This is the issue date, not the accrual date. It moves *backwards* when the most recent document stops counting; see `invoice_count`."
        }
      }
    },
    "Pagination": {
      "type": "object",
      "required": [
        "current_page",
        "total_pages",
        "total_items",
        "items_per_page"
      ],
      "properties": {
        "current_page": {
          "type": "integer"
        },
        "total_pages": {
          "type": "integer",
          "description": "How many pages the query has. An empty collection has **one** page — the\nfirst one, empty — so the smallest value a canonical route returns is `1`.\n\nThe deprecated flat aliases (`/v1/invoices`, `/v1/customers`, …) answer `0`\nfor that same empty collection, and `has_next`/`has_previous` follow suit.\nThey were left as they were on purpose: a client that reads `total_pages == 0`\nas \"no results\" would break if it changed under it. Do not compare the two\nfamilies of routes field by field; read `total_items` if what you want to know\nis whether anything came back.\n"
        },
        "total_items": {
          "type": "integer"
        },
        "items_per_page": {
          "type": "integer"
        },
        "has_next": {
          "type": "boolean"
        },
        "has_previous": {
          "type": "boolean"
        }
      }
    },
    "ResponseMeta": {
      "type": "object",
      "properties": {
        "timestamp": {
          "type": "string",
          "format": "date-time"
        },
        "request_id": {
          "type": "string"
        }
      }
    }
  }
}

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/beel-es-list-company-stats200-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.