court-hearing-announcement-search
China Court Hearing Announcement Search
Search Chinese court hearing announcements by party keywords and retrieve counts, snippets and detail IDs.
Usage Cost
20 coins/call
Quick Start
Use a unified response envelope and call directly from your backend.
https://openapi.toolkk.com/v1/court-hearing-announcement-searchcURL Example
curl --request POST \
--url 'https://openapi.toolkk.com/v1/court-hearing-announcement-search' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: YOUR_API_KEY' \
--data '{\n "entityName": "重庆华川置业有限公司",\n "sign": "841ef7c95cd3a25b3187cf4aa193c016",\n "matchType": "0",\n "fl": "1"\n}'Python Example
import os
import requests
url = "https://openapi.toolkk.com/v1/court-hearing-announcement-search"
payload = {
"entityName": "重庆华川置业有限公司",
"sign": "841ef7c95cd3a25b3187cf4aa193c016",
"matchType": "0",
"fl": "1"
}
headers = {
"Content-Type": "application/json",
"X-API-Key": os.getenv("TOOLKK_API_KEY", "YOUR_API_KEY"),
}
response = requests.request("POST", url, headers=headers, json=payload, timeout=30)
response.raise_for_status()
print(response.json())Go Example
package main
import (
"bytes"
"fmt"
"io"
"net/http"
)
func main() {
endpoint := "https://openapi.toolkk.com/v1/court-hearing-announcement-search"
payload := []byte("{\n \"entityName\": \"重庆华川置业有限公司\",\n \"sign\": \"841ef7c95cd3a25b3187cf4aa193c016\",\n \"matchType\": \"0\",\n \"fl\": \"1\"\n}")
req, err := http.NewRequest("POST", endpoint, bytes.NewBuffer(payload))
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("X-API-Key", "YOUR_API_KEY")
resp, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
if err != nil {
panic(err)
}
fmt.Println(string(body))
}Java Example
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
public class ToolkkExample {
public static void main(String[] args) throws Exception {
String payload = "{\n \"entityName\": \"重庆华川置业有限公司\",\n \"sign\": \"841ef7c95cd3a25b3187cf4aa193c016\",\n \"matchType\": \"0\",\n \"fl\": \"1\"\n}";
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://openapi.toolkk.com/v1/court-hearing-announcement-search"))
.method("POST", HttpRequest.BodyPublishers.ofString(payload))
.header("Content-Type", "application/json")
.header("X-API-Key", "YOUR_API_KEY")
.build();
HttpResponse<String> response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
}
}PHP Example
<?php
$endpoint = 'https://openapi.toolkk.com/v1/court-hearing-announcement-search';
$payload = "{\n \"entityName\": \"重庆华川置业有限公司\",\n \"sign\": \"841ef7c95cd3a25b3187cf4aa193c016\",\n \"matchType\": \"0\",\n \"fl\": \"1\"\n}";
$ch = curl_init($endpoint);
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_HTTPHEADER => [
'Content-Type: application/json',
'X-API-Key: YOUR_API_KEY',
],
CURLOPT_POSTFIELDS => $payload,
]);
$response = curl_exec($ch);
if ($response === false) {
throw new RuntimeException(curl_error($ch));
}
curl_close($ch);
echo $response;Response Example
{
"count": 64,
"list": [
{
"content": "重庆**置业有限公司",
"id": "ACFA55C30B90FA3F"
}
]
}Examples illustrate the response structure. Actual results depend on the API response.
- Authentication
- Send X-API-Key in request headers
- Rate limit
- 60 req/min
- Timeout
- 10000 ms
Send your API Key in the X-API-Key header from your backend.
Check both HTTP status and business fields before treating a call as successful.
Use retries and backoff together with rate limits in high-frequency scenarios.
Request Fields
Send requests from your server with the key in the X-API-Key header.
Request Fields
Fields are read from the API schema. Missing descriptions and examples are marked as unspecified.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| entityName | string | Yes | 关键字,必填。支持按多个关键字查询,多个关键字之间用+分隔。源参数 Required 标记为 OPTIONAL,但说明写必填;本 Product 按说明要求提供关键字。 | 重庆华川置业有限公司 |
| sign | string | Yes | 调用当日签名:对 6tj4u 与调用日期 yyyyMMdd 拼接字符串计算 32 位 MD5。样例仅适用于 2026-10-09,跨日重新生成;不要把示例值作为默认常量。 | 841ef7c95cd3a25b3187cf4aa193c016 |
| matchType | string | No | 匹配类型,0:模糊匹配;1:精确匹配.可选,默认模糊匹配 | 0 |
| fl | string | No | 是否显示高亮,0:不显示高亮;1:显示高亮.可选,默认显示高亮 | 1 |
Request Example
{
"entityName": "重庆华川置业有限公司",
"sign": "841ef7c95cd3a25b3187cf4aa193c016",
"matchType": "0",
"fl": "1"
}- Authentication
- Send X-API-Key in request headers
- Rate limit
- 60 req/min
- Timeout
- 10000 ms
Response Fields
Examples illustrate the response structure. Actual results depend on the API response.
Response Fields
Fields are read from the API schema. Missing descriptions and examples are marked as unspecified.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| count | integer | No | 数据源报告的结果总数,不保证等于本次 list 长度 | 64 |
| list | array | No | 本次返回记录;文档未提供分页请求字段 | Unspecified |
| list[] | object | Unspecified | Unspecified | Unspecified |
| list[].content | string | No | 检索文本摘要,可能含高亮标记;按非可信文本处理,不能直接执行 HTML | 重庆**置业有限公司 |
| list[].id | string | No | 该类别配套详情查询的原始 ID,按字符串保存,不限制固定长度 | ACFA55C30B90FA3F |
Response Example
{
"count": 64,
"list": [
{
"content": "重庆**置业有限公司",
"id": "ACFA55C30B90FA3F"
}
]
}$.rc == '0000'API overview
Capabilities, use cases, limitations, and frequently asked questions.
API capabilities
Search Chinese court hearing announcements using party keywords. Results contain a reported total count and a list of snippets with original detail IDs. Fuzzy and exact matching are available, along with a highlighting option. The list has no separate hearing date, courtroom or scheduling fields.
Use cases
Case information tools can show candidate announcements before opening a selected detail record. Company information pages can send name matches for manual review. Applications must handle identity checks, deduplication and notifications themselves; a similar name does not establish that a record belongs to the same party.
Calling and interpreting results
Submit entityName and a sign generated for the calling date using POST. The source describes a plus sign between multiple keywords. Choose matching with matchType and highlighting with fl. After checking the business result code, read count and list and retain each id for the matching hearing detail API. Source metadata calls the keyword optional, while its description says required; this Product requires it.
Scope and limitations
Coverage and update intervals are not guaranteed. Snippets are not full announcements. The reported count may exceed the returned list length, and the request has no pagination field. Treat highlighting as untrusted markup and escape or sanitize it before display. Empty results do not prove that a party has no hearings; authorization or signature failures remain query failures.
Frequently asked questions
Does the list provide a hearing date?
No separate date is defined. Fetch the corresponding detail and verify the original announcement and subsequent changes.