TW Market Data LogoTW Market Data

Building an AI agent? Start with /llms.txt for the full site index.

Companies & Events

Attention & disposition events

Attention & disposition events

VerifiedSource: TWSE / TPEx·Plan: pro·Cost: 2 credits·GET /v2/datasets/attention-disposal-events

Attention & disposition events is a Taiwan market dataset sourced from TWSE / TPEx, served by TW Market Data as GET /v2/datasets/attention-disposal-events.

Overview

Attention & disposition events — grain: ticker / event_date.

FieldTypeDescription
tickerstring
company_namestring
marketstring
event_datestring
event_typestring
reasonstring
period_startnull
period_endnull
measuresobject
article_clausestring
date_semanticsstring

Example response

A real response from this endpoint. Rows are returned under "data", and provenance is carried in the shape shown below — it is not identical across datasets, so read this page's rather than assuming another's.

{  "dataset_id": "attention_disposal_events",  "request_context": {    "scope": "twse_tpex_attention_and_disposal_events",    "coverage_type": "event_driven",    "filters": {      "ticker": "9103",      "market": null,      "event_type": null,      "event_date": null,      "date_from": null,      "date_to": null,      "limit": 50    },    "min_event_date": "2025-09-09",    "max_event_date": "2026-08-05"  },  "quality": {    "row_count": 50,    "ticker_count": 1,    "event_type_count": 2,    "sensitive_fields_exposed": false  },  "lineage": {    "source_names": [      "TWSE attention notice",      "TWSE disposition notice"    ],    "semantics": "<Chinese value - see the zh page>"  },  "error": null,  "data": [    {      "ticker": "9103",      "company_name": "<Chinese value - see the zh page>",      "market": "TWSE",      "event_date": "2026-08-05",      "event_type": "attention",      "reason": "<Chinese value - see the zh page>",      "period_start": null,      "period_end": null,      "measures": {        "pe_ratio": null,        "close_price": 5.3,        "cumulative_count": 8      },      "article_clause": "<Chinese value - see the zh page>",      "date_semantics": "event_date_from_notice_row",      "source_name": "TWSE attention notice",      "source_url": "https://www.twse.com.tw/announcement/notice?response=json&startDate=20260621&endDate=20260805",      "source_authority": "TWSE official announcement",      "event_version": "twse_attention_notice_v1",      "lineage": {        "emitter": "build_attention_disposal_daily_candidates",        "variant": "twse_attention"      }    },    {      "ticker": "9103",      "company_name": "<Chinese value - see the zh page>",      "market": "TWSE",      "event_date": "2026-07-23",      "event_type": "attention",      "reason": "<Chinese value - see the zh page>",      "period_start": null,      "period_end": null,      "measures": {        "pe_ratio": null,        "close_price": 5.73,        "cumulative_count": 7      },      "article_clause": "<Chinese value - see the zh page>",      "date_semantics": "event_date_from_notice_row",      "source_name": "TWSE attention notice",      "source_url": "https://www.twse.com.tw/announcement/notice?response=json&startDate=20260620&endDate=20260804",      "source_authority": "TWSE official announcement",      "event_version": "twse_attention_notice_v1",      "lineage": {        "emitter": "build_attention_disposal_daily_candidates",        "variant": "twse_attention"      }    }  ],  "data_count": 50,  "known_gaps": [    "reason_text_is_free_prose_not_a_coded_category",    "twse_and_tpex_publish_under_separate_rulebooks",    "event_version_increments_when_an_event_is_restated"  ],  "warnings": [    "not_investment_advice"  ],  "envelope": {    "dataset_id": "attention_disposal_events",    "scope": "twse_tpex_attention_and_disposal_events",    "row_count": 50  }}

Captured from the live API on 2026-07-20.

Chinese data values are shown as a marker here so this page stays in English; the /zh page shows them verbatim.

Provenance

These columns are returned alongside the data and record where the row came from. They are provenance, not the dataset's subject matter, so they are listed here rather than in the field table.

source_namesource_urlsource_authorityevent_versionlineage

Related datasets

Datasets that join with this one. The key each pair aligns on is shown, so you can plan a multi-table query without guessing.

Getting started

  1. Put your key in the X-API-Key header.
  2. Add query parameters (symbol, date range, limit).
  3. Send the request and read the data array.
curl "https://api.twmarketdata.com/v2/datasets/attention-disposal-events?symbol=2330" \  -H "X-API-Key: sk_live_..."

Filtering

ParameterRequiredTypeDescription
symbolYesstringTicker, e.g. 2330.
start_dateNostring (YYYY-MM-DD)Start of the query range.
end_dateNostring (YYYY-MM-DD)End of the query range.
limitNointegerMaximum rows to return.

Python

A first call:

import requests resp = requests.get(    "https://api.twmarketdata.com/v2/datasets/attention-disposal-events",    params={"symbol": "2330"},    headers={"X-API-Key": "sk_live_..."},)resp.raise_for_status()print(resp.json()["data"])

With a date-range filter:

import requests # The full verified example — the same call with every supported filter set.resp = requests.get(    "https://api.twmarketdata.com/v2/datasets/attention-disposal-events",    params={"symbol": "2330"},    headers={"X-API-Key": "sk_live_..."},)resp.raise_for_status()for row in resp.json()["data"]:    print(row)

OpenAPI

This endpoint is GET /v2/datasets/attention-disposal-events. The full machine-readable schema (parameters, security, response envelope) lives in the OpenAPI spec.

Notes & limitations

  • event_date is the date the attention/disposition takes effect, and the announcement precedes it. This dataset carries no announcement-date column, so using event_date as the knowledge axis would treat a not-yet-announced disposition as known; as_of is refused for that reason and a backtest must align to the announcement date itself.