Enterprise Annual Report Details API

Retrieve structured details of an enterprise annual report for a specified year using the enterprise ID or unified social credit code and the reporting year. Supply a year. Sample fields include status information and names. Use it for account research or company due diligence. The GET request schema also lists tyshxydm.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Annual report year (corresponding to ES `reportYear`)
Enterprise ID
Unified social credit code

Sample response

{
  "code": 200,
  "data": {
    "id": "a80a4cc8-9954-4dd3-bcaf-aebb99487b14",
    "name": "示例科技有限公司",
    "企业基本信息": {
      "从业人数": "企业选择不公示",
      "企业名称": "示例科技有限公司",
      "企业经营状态": "开业",
      "企业通信地址": "北京市海淀区示例路1号",
      "企业邮箱": "企业选择不公示",
      "工商注册号": "110000000000001",
      "统一社会信用代码": "91110000000000000X",
      "联系电话": "010-12345678"
    },
    "企业资产信息": {
      "主营业务收入": "企业选择不公示",
      "净利润": "企业选择不公示",
      "利润总额": "企业选择不公示",
      "所有者权益合计": "企业选择不公示",
      "纳税总额": "企业选择不公示",
      "负债总额": "企业选择不公示",
      "资产总额": "企业选择不公示",
      "销售总额(营业总收入)": "企业选择不公示"
    },
    "对外投资信息": [],
    "对外担保信息": [],
    "网站或网店信息": [],
    "股东及出资信息": []
  },
  "message": "请求成功",
  "status": "success"
}

Response result

Response structure

Inferred from examples
  • codeinteger
  • dataobject
    • idstring
    • namestring
    • 企业基本信息object
      • 从业人数string
      • 企业名称string
      • 企业经营状态string
      • 企业通信地址string
      • 企业邮箱string
      • 工商注册号string
      • 统一社会信用代码string
      • 联系电话string
    • 企业资产信息object
      • 主营业务收入string
      • 净利润string
      • 利润总额string
      • 所有者权益合计string
      • 纳税总额string
      • 负债总额string
      • 资产总额string
      • 销售总额(营业总收入)string
    • 对外投资信息unknown[]
    • 对外担保信息unknown[]
    • 网站或网店信息unknown[]
    • 股东及出资信息unknown[]
  • messagestring
  • statusstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Enterprise Annual Report Details API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.