Enterprise Hearing Notice List API

Retrieve hearing notices for an enterprise using its enterprise ID or unified social credit code with the Yuandian API. Results are paginated, with 30 records per page by default. Use it for account research or company due diligence. The GET request schema also lists tyshxydm, pageNo.

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
Enterprise ID
Unified social credit code
Page number; defaults to 1

Sample response

{
  "code": 200,
  "data": {
    "hasMore": false,
    "id": "902490e5-1c92-46a3-9032-7eda9b2ff335",
    "list": [
      {
        "审理时间": "2024年08月26日",
        "审理法院": "海宁市人民法院",
        "应诉方": [
          "被褚昔彭",
          "祝高松",
          "余文珍",
          "高雪芬"
        ],
        "起诉方": [
          "上海苗发金属材料有限公司"
        ]
      },
      {
        "审理时间": "2023年08月14日",
        "审理法院": "上海市宝山区人民法院",
        "应诉方": [
          "海宁市远东环保设备科技有限公司",
          "褚列平",
          "褚昔彭"
        ],
        "案由": "案由:买卖合同纠纷&承办部门:商事审判庭&审判长/主审人:王经珍",
        "起诉方": [
          "上海苗发金属材料有限公司"
        ]
      },
      {
        "审理时间": "2023年07月13日",
        "审理法院": "上海市宝山区人民法院",
        "应诉方": [
          "海宁市远东环保设备科技有限公司",
          "褚列平",
          "诸昔彭"
        ],
        "案由": "案由:买卖合同纠纷&承办部门:商事审判庭&审判长/主审人:王经珍",
        "起诉方": [
          "上海苗发金属材料有限公司"
        ]
      }
    ],
    "name": "上海苗发金属材料有限公司",
    "pageNo": 1,
    "pageSize": 50,
    "total": 3
  },
  "message": "请求成功",
  "status": "success"
}

Response result

Response structure

Inferred from examples
  • codeinteger
  • dataobject
    • hasMoreboolean
    • idstring
    • listobject[]
      • 审理时间string
      • 审理法院string
      • 应诉方string[]
      • 起诉方string[]
      • 案由string
    • namestring
    • pageNointeger
    • pageSizeinteger
    • totalinteger
  • 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 Hearing Notice List API with your agent

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