Release 0.0.1

Deprecated /indicators routes (except Industry TSI) are replaced by proof-points, facts, and manifestations. Includes a copy-paste LLM prompt to migrate a codebase.

Most /indicators/* endpoints are deprecated. They still respond so existing integrations keep working, but new work should use Proof Points, Facts, and Manifestations.

Industry TSI is unchanged: GET /indicators/industry-tsi/time-series.

What replaced indicators

Use this when you need	New API
Indexed documents (patents, news, research, earnings calls, PDFs, grants/projects)	Proof Points — `POST /proof-points/...`
Knowledge-graph organizations, investments, acquisitions	Facts — `POST /facts/...`
Grouped events (partnerships, product launches, mixed types)	Manifestations — `POST /manifestations/search`
Industry trend strength	Industry TSI

Endpoint map

Deprecated	Replacement
`GET /indicators/organizations/time-series`	`POST /facts/organizations/time-series`
`GET /indicators/organizations/proof-points`	`POST /facts/organizations/search`
`GET /indicators/investments/time-series`	`POST /facts/investments/time-series`
`GET /indicators/investments/proof-points`	`POST /facts/investments/search`
`GET /indicators/acquisitions/time-series`	`POST /facts/acquisitions/time-series`
`GET /indicators/acquisitions/proof-points`	`POST /facts/acquisitions/search`
`POST /indicators/news-articles/proofpoints`	`POST /proof-points/news-articles/search`
`POST /indicators/news-articles/time-series`	`POST /proof-points/news-articles/time-series`
`POST /indicators/patents/proofpoints`	`POST /proof-points/patents/search`
`POST /indicators/patents/time-series`	`POST /proof-points/patents/time-series`
`POST /indicators/research-articles/proofpoints`	`POST /proof-points/research-articles/search`
`POST /indicators/research-articles/time-series`	`POST /proof-points/research-articles/time-series`
`POST /indicators/earnings-calls/proofpoints`	`POST /proof-points/earnings-calls/search`
`POST /indicators/earnings-calls/time-series`	`POST /proof-points/earnings-calls/time-series`
`POST /indicators/grants/proofpoints`	`POST /proof-points/projects/search`
`POST /indicators/grants/time-series`	`POST /proof-points/projects/time-series`
`POST /indicators/consultancy-reports/proofpoints`	`POST /proof-points/pdfs/search`
`POST /indicators/consultancy-reports/time-series`	`POST /proof-points/pdfs/time-series`
`POST /indicators/partnerships/proofpoints`	`POST /manifestations/search` with `types: ["partnership"]`
`POST /indicators/partnerships/time-series`	`POST /manifestations/search`, or news-articles time series with `mentionsEvents: ["partnership"]`
`POST /indicators/product-launches/proofpoints`	`POST /manifestations/search` with `types: ["product-launch"]`
`POST /indicators/product-launches/time-series`	`POST /manifestations/search`, or news-articles time series with `mentionsEvents: ["product-launch"]`
`GET /indicators/industry-tsi/time-series`	Unchanged
`GET /indicators/*/summary-statistics`	No replacement

Some old document routes used /proofpoints (no hyphen) and some fact routes used /proof-points. Both are deprecated; new document search lives under /proof-points/{type}/search.

Breaking request changes

Nested FilterClause trees (type: "and", clauses: [...]) become a flat JSON body: query, topicIds, organizationIds, start, end.
Organization, investment, and acquisition indicators were GET + query params. Replacements are POST + JSON body.
Grants interval_overlap is not on /proof-points/projects. There, start / end are published-date bounds. Project startDate / endDate are still on each record.
Proof points and facts page with skip / take. Manifestations page with cursor / take.
Response shapes differ: enriched documents vs fact records vs manifestations with references.

Schemas for the new operations are in the OpenAPI spec and the API reference. Machine-readable docs: /llms-full.txt.

Paste the prompt below into Cursor, ChatGPT, or another coding agent in the repository that calls Connect. It tells the agent to load the live OpenAPI spec and apply the mapped endpoints instead of guessing field names.

Migrate this codebase off deprecated Trendtracker Connect API `/indicators/*` callers onto Proof Points, Facts, and Manifestations.

Source of truth (fetch these; do not invent schemas):
- OpenAPI JSON: https://connect-api.trendtracker.ai/openapi.json
  (If CONNECT_API is set, use `{CONNECT_API}/openapi.json` instead.)
- Release note with this mapping: Connect API docs "Release 0.0.1".
- Optional crawl: the docs host `/llms-full.txt`.

Rules:
1. Find every HTTP call, client method, type, fixture, and test that hits
   `/indicators/...` including `proofpoints`, `proof-points`, `time-series`,
   and `summary-statistics`.
2. Leave `GET /indicators/industry-tsi/time-series` unchanged.
3. Rewrite each other caller to the mapped replacement below. Use the
   OpenAPI `requestBody` / `parameters` / response schema of the NEW
   operation (POST JSON, camelCase aliases, required fields). Prefer the
   spec over this table if they disagree on field names. Do not invent
   query parameters the spec does not define.
4. Flatten old nested FilterClause trees (`type: "and"|"or"|"query"|
   "interval_overlap"|...`) into the new flat filters (`query`, `topicIds`,
   `organizationIds`, `start`, `end`, plus type-specific fields).
5. Switch GET + query-string fact indicators to POST + JSON body.
6. Update tests and fixtures. Report any caller you could not map,
   including `summary-statistics` (no replacement).

Endpoint map:
GET  /indicators/organizations/time-series       → POST /facts/organizations/time-series
GET  /indicators/organizations/proof-points      → POST /facts/organizations/search
GET  /indicators/investments/time-series         → POST /facts/investments/time-series
GET  /indicators/investments/proof-points        → POST /facts/investments/search
GET  /indicators/acquisitions/time-series        → POST /facts/acquisitions/time-series
GET  /indicators/acquisitions/proof-points       → POST /facts/acquisitions/search
POST /indicators/news-articles/proofpoints       → POST /proof-points/news-articles/search
POST /indicators/news-articles/time-series       → POST /proof-points/news-articles/time-series
POST /indicators/patents/proofpoints             → POST /proof-points/patents/search
POST /indicators/patents/time-series             → POST /proof-points/patents/time-series
POST /indicators/research-articles/proofpoints   → POST /proof-points/research-articles/search
POST /indicators/research-articles/time-series   → POST /proof-points/research-articles/time-series
POST /indicators/earnings-calls/proofpoints      → POST /proof-points/earnings-calls/search
POST /indicators/earnings-calls/time-series      → POST /proof-points/earnings-calls/time-series
POST /indicators/grants/proofpoints              → POST /proof-points/projects/search
POST /indicators/grants/time-series              → POST /proof-points/projects/time-series
POST /indicators/consultancy-reports/proofpoints → POST /proof-points/pdfs/search
POST /indicators/consultancy-reports/time-series → POST /proof-points/pdfs/time-series
POST /indicators/partnerships/proofpoints        → POST /manifestations/search (types: ["partnership"])
POST /indicators/partnerships/time-series        → POST /manifestations/search, or POST /proof-points/news-articles/time-series with mentionsEvents: ["partnership"]
POST /indicators/product-launches/proofpoints    → POST /manifestations/search (types: ["product-launch"])
POST /indicators/product-launches/time-series    → POST /manifestations/search, or POST /proof-points/news-articles/time-series with mentionsEvents: ["product-launch"]
GET  /indicators/industry-tsi/time-series        → unchanged

Release 0.0.1

What replaced indicators

Endpoint map

Breaking request changes

Migrate with an LLM

On this page