Tianyancha Company Dynamics avatar

Tianyancha Company Dynamics

Pricing

$3.00 / 1,000 company dynamics

Go to Apify Store
Tianyancha Company Dynamics

Tianyancha Company Dynamics

Fetches a company's recent dynamics (诉讼, 变更, 处罚等) from Tianyancha (天眼查) by company gid.

Pricing

$3.00 / 1,000 company dynamics

Rating

0.0

(0)

Developer

NewLai

NewLai

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

What does tianyancha-dynamics do? | 天眼查企业动态与风险监控

tianyancha-dynamics is a Chinese company event and legal risk monitoring scraper. Given a company gid, it extracts recent events from Tianyancha (天眼查) — lawsuits, court hearing announcements, administrative penalties, company record changes, event dates, and risk levels — as structured JSON.

中文简介: 这是一个用于天眼查企业动态查询和企业风险监控的 API,可批量采集工商变更、法律诉讼、开庭公告、行政处罚及风险等级,适用于合规审查、供应商监控、企业尽调和风险预警。

Each event becomes its own dataset row tagged with company ID, event type, date, and risk level. Run one-off checks in Apify Console or build recurring alerts with the Apify API, schedules, webhooks, monitoring, and integrations.

Why use tianyancha-dynamics?

  • No browser, no manual login — plain HTTP requests, so runs are fast and cheap.
  • Clean structured JSON — every event is flattened into its own dataset row, downloadable as JSON, CSV, Excel, XML, or HTML.
  • Batch by company — fetch many gids in a single run; every event lands in the same dataset.
  • Ready for automation — combine it with Apify scheduling, webhooks, and API access to power risk-monitoring and compliance pipelines.
  • Apify platform advantages — monitored runs, pay-per-use billing, proxy support, and 15 integrations out of the box.

These Actors share a gid-based workflow. Start with Tianyancha Company Search to find companies by keyword, then pass each returned id to the detail Actors below.

中文工作流: 先用天眼查企业查询按关键词获取公司 gid,再把 gid 传给其他 Actor,组合完成工商、股东、动态、风险、知识产权和上市信息查询。

ActorBest for / 用途
Tianyancha Company Search / 天眼查企业查询Find companies by keyword and return reusable gid values / 按关键词查公司
Tianyancha Basic Company Info / 天眼查工商信息Company profile, legal representative, capital, credit code, and address / 企业工商档案
Tianyancha Shareholders / 天眼查股东信息Shareholders, holding percentages, controlling shareholder, and actual controller / 股权结构
Tianyancha Company Dynamics / 天眼查企业动态Company changes, lawsuits, court hearings, penalties, and alerts / 企业风险动态
Tianyancha Risk & IP Counts / 天眼查风险与知识产权Lawsuit, penalty, patent, trademark, branch, and risk counts / 风险与知识产权统计
Tianyancha Listed Company Data / 天眼查上市信息Stock code, exchange, market board, listing status, and market cap / 上市公司与股票信息

How to use tianyancha-dynamics

  1. Open the Actor's Input tab in the Apify Console.
  2. Enter one or more company gids (e.g. [9519792, 9519793]).
  3. Click Start. The Actor fetches each company's dynamics and stores them in the run's dataset.
  4. Open the run's Dataset tab to preview the JSON, or download it in your preferred format.

You can also run it from the command line with the Apify CLI:

$apify call <username>/tianyancha-dynamics --input '{"gids": [9519792, 9519793]}'

Input

The Actor takes a single input field:

FieldTypeRequiredDescription
gidsarray<integer>YesTianyancha company group IDs (gids) to fetch, e.g. [9519792, 9519793]

Example input:

{
"gids": [9519792, 9519793]
}

All Tianyancha API requests use Apify Residential Proxy with the exit location fixed to mainland China (CN). No custom proxy URL or proxy environment variable is required. The Actor fails instead of falling back to a direct request.

The remaining runtime option is preset in the Actor configuration:

VariableDescription
TYC_CONCURRENCYMaximum number of companies fetched concurrently. Preset and fallback: 8.

Output

The Actor pushes one record per dynamic event to the default dataset. A representative (abbreviated) output item looks like:

{
"gid": 9519792,
"eventType": "新增开庭公告",
"dynamicDate": "2026-08-16",
"riskLevel": 4,
"textList": [
{ "text": "新增开庭公告,案由:侵害作品信息网络传播权纠纷", "display": true }
]
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data table

Main fields you can expect in the output:

FieldDescription
gidTianyancha company ID
eventTypeType of the dynamic event
dynamicDateDate the event occurred
textListHuman-readable description lines
riskLevelRisk level (higher = more severe)
dimTypeInternal dimension type code
appRouteUrlIn-app deep-link to the event

How much does it cost to scrape Tianyancha?

This Actor uses pay-per-event pricing at $0.003 per successfully processed company (gid). The number of records, pages, articles, shareholders, events, or listing items returned for that company does not change the price.

Successfully processed companiesEvent charge
1$0.003
2$0.006
10$0.030
100$0.300

A company is charged only after Tianyancha returns a valid response and all output records for that gid are saved to the Dataset. Failed requests, restricted/error responses, and Dataset write failures are not charged. A valid response with zero matching detail records is still a completed company lookup and is charged once. Duplicate input gid values are normalized and processed only once.

Tips or Advanced options

  • Get the right gid — pair this with the tianyancha-search Actor to find companies by keyword, then feed their ids here.
  • Batch lookups — pass many gids in a single run; every event is stored in the same dataset.
  • Fast and cheap — the Actor uses plain HTTP, so it is far cheaper and faster than browser-based scrapers for the same data.

FAQ, disclaimers, and support

  • Is this legal? The Actor accesses Tianyancha's public mobile API. You are responsible for complying with Tianyancha's Terms of Service and applicable laws, and for how you use the data.
  • Known limitations — the private API may change without notice; if the endpoint changes, runs may fail until the Actor is updated.
  • Need a custom solution? For tailored scraping, bulk export, or integration work, open an issue on the Issues tab or reach out for a custom Actor.

This page was generated with Apify's Actor README guidelines.