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...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
yuandianCurrent Enterprise Litigation Document List API · GET | $0 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
codeintegerdataobjecthasMorebooleanidstringlistobject[]审判程序string应诉方string[]文书idstring文书种类string时间string标题string案号string案由string第三方unknown[]裁判结果string起诉方string[]
namestringpageNointegerpageSizeintegertotalinteger
messagestringstatusstring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
code?: number;
data?: {
hasMore?: boolean;
id?: string;
list?: Array<{
"审判程序"?: string;
"应诉方"?: Array<string>;
"文书id"?: string;
"文书种类"?: string;
"时间"?: string;
"标题"?: string;
"案号"?: string;
"案由"?: string;
"第三方"?: Array<unknown>;
"裁判结果"?: string;
"起诉方"?: Array<string>;
}>;
name?: string;
pageNo?: number;
pageSize?: number;
total?: number;
};
message?: string;
status?: string;
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/yuandian/open/rh_enterpriseWritList- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/yuandian/open/rh_enterpriseWritList?id=a80a4cc8-9954-4dd3-bcaf-aebb99487b14&pageNo=1' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
id | URL query parametersquery | string | No | Enterprise ID (primary table `legal_insight_qyfx_company`, document `_id`) |
tyshxydm | URL query parametersquery | string | No | Unified social credit code |
pageNo | URL query parametersquery | integer | No | Page number; defaults to 1 |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Configured HTTP 200; actual status is unverified. Example from the provider's documentation. Field values in your results will differ.
{
"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"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# 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.
## Available implementations
yuandian · Enterprise Litigation Document List API: https://openany.si/markets/apis/capabilities/yuandian-enterprise-litigation-document-list-api?offering=7e9e9424-5b01-4f7b-bc31-74559b551f63 · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/yuandian-enterprise-litigation-document-list-api
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/yuandian/open/rh_enterpriseWritList
Price: $0 / call
Provider: yuandian
Contract revision: 4
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/yuandian/open/rh_enterpriseWritList?id=a80a4cc8-9954-4dd3-bcaf-aebb99487b14&pageNo=1' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "Enterprise Litigation Document List API",
"endpoint": "https://api.openany.si/v1/agent-apis/yuandian/open/rh_enterpriseWritList",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Enterprise ID (primary table `legal_insight_qyfx_company`, document `_id`)",
"location": "query",
"name": "id",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Unified social credit code",
"location": "query",
"name": "tyshxydm",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Page number; defaults to 1",
"location": "query",
"name": "pageNo",
"nullable": false,
"required": false,
"type": "integer"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "0",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Official example (abridged; HTTP assumed)",
"request": {
"body": null,
"headers": {},
"path": {},
"query": {
"id": "a80a4cc8-9954-4dd3-bcaf-aebb99487b14",
"pageNo": "1"
}
},
"response_body": {
"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"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Official example (abridged; HTTP assumed)
Example from the provider's documentation. Field values in your results will differ.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 3
Review these request fields before running. Keep the published provider and request method unchanged.
id- Enterprise ID (primary table `legal_insight_qyfx_company`, document `_id`)
tyshxydm- Unified social credit code
pageNo- Page number; defaults to 1
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/yuandian/open/rh_enterpriseWritList?id=a80a4cc8-9954-4dd3-bcaf-aebb99487b14&pageNo=1' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Configured HTTP 200; actual status is unverified.
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" }
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.