/hkexnews/exchange_reports/repurchases

POST /api/hkexnews/exchange_reports/repurchases

Price: 20 credits

Share repurchases reported to the Hong Kong Exchange by listed issuers, from the Exchange's daily share repurchase reports: the security, trading day, number of shares bought back, price range, amount paid, method, and the cumulative figures under the repurchase mandate.

How to use it

Newest report first, covering reports from January 2014. Pass report_date_from and report_date_to to read a specific period, and stock_code to follow one issuer's buybacks. With stock_code the window spans at most 183 days, by default the 183 days up to report_date_to or today. Cumulative mandate figures appear on an issuer's last row of a report.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of repurchase rows to return (min: 1; max: 10000)
• report_date_from integer nullable — Earliest report day, as unix seconds; day-granular (examples: 1756684800)
• report_date_to integer nullable — Latest report day, as unix seconds; day-granular (examples: 1759190400)
• stock_code string nullable — HKEX stock code to keep (examples: "00700", "1530"; minLength: 1; maxLength: 5)

Response

• @type string (default: "HkexnewsShareRepurchase")
• stock_code string nullable
• company_name string nullable
• security_type string nullable
• report_date integer nullable
• trading_date integer nullable
• shares_repurchased number nullable
• currency string nullable
• highest_price number nullable
• lowest_price number nullable
• aggregate_price number nullable
• method string nullable
• total_shares_repurchased number nullable
• shares_for_cancellation number nullable
• shares_for_treasury number nullable
• shares_repurchased_under_mandate number nullable
• percent_of_issued_shares_under_mandate number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.