Enterprise Litigation Document List API

Retrieve enterprise Litigation Document List with the Yuandian API. The request accepts a page number when provided. Use it in a legal research or due diligence workflow. The GET request schema also lists id, tyshxydm, pageNo. Use the results to organize a research workflow and cross-check the relevant source records.

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 (primary table `legal_insight_qyfx_company`, document `_id`)
Unified social credit code
Page number; defaults to 1

Sample response

{
  "code": 200,
  "data": {
    "hasMore": true,
    "id": "a80a4cc8-9954-4dd3-bcaf-aebb99487b14",
    "list": [
      {
        "审判程序": "一审",
        "应诉方": [
          "乙公司"
        ],
        "文书id": "xxx",
        "文书种类": "判决书",
        "时间": "2024-06-01",
        "标题": "……",
        "案号": "(2024)京0105民初123号",
        "案由": "侵害商标权纠纷",
        "第三方": [],
        "裁判结果": "……",
        "起诉方": [
          "甲公司"
        ]
      }
    ],
    "name": "北京百度网讯科技有限公司",
    "pageNo": 1,
    "pageSize": 30,
    "total": 120
  },
  "message": "请求成功",
  "status": "success"
}

Response result

Response structure

Inferred from examples
  • codeinteger
  • dataobject
    • hasMoreboolean
    • idstring
    • listobject[]
      • 审判程序string
      • 应诉方string[]
      • 文书idstring
      • 文书种类string
      • 时间string
      • 标题string
      • 案号string
      • 案由string
      • 第三方unknown[]
      • 裁判结果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 Litigation Document List API with your agent

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