---
title: "Intelligence Impact"
method: GET
path: "/api/intelligence/v1/impact/{ticker}"
tags: ["Intelligence API"]
---

# Intelligence Impact

`GET /api/intelligence/v1/impact/{ticker}`

## Request

- Base URL: `https://api.xfinlab.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.xfinlab.com/api/intelligence/v1/impact/{ticker}`
- Auth: none declared

2026-09-30 (AJ: monetization gap-analysis session -- asked "重有咩
有差距的可收費", identified relationship/impact data as the one
genuinely missing, genuinely buildable, genuinely differentiated
layer vs. generic financial data APIs that only sell price +
fundamentals): given a ticker, who is upstream (suppliers),
downstream (customers), same-sector (peers), and directly competing
(competitors) -- plus market-wide capital flow and this ticker's
CFTC futures-positioning context if applicable, composed from
services/relationship_graph_service.py, services/capital_flow_
engine.py, and services/cftc_cot_service.py (all pre-existing, real
data sources -- nothing new fetched here, just a new composition).

Supplier/customer/competitor relationships are a hand-curated
STARTING set (see relationship_graph_service.py's module docstring
for sourcing and scope) -- a ticker outside that set returns an
honest empty list for those three fields (never a guess), while
sector_peers still populates from the existing sector-tagged US
basket for any US large-cap ticker.

## Path parameters

- `ticker` string, required

## Headers

- `X-API-Key` string

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/xfinlab/apis/xfinlab-api.md) · [All operations](https://skmtc.dev/xfinlab/apis/xfinlab-api/llms.txt) · [OpenAPI document](https://skmtc.dev/xfinlab/apis/xfinlab-api/revisions/205f85614bc6?raw)