Flock

Flock API

India + US disclosure data, as an API.

Normalised regulatory disclosures — entities, holdings, filings, announcements, and multi-entity disclosure overlap — as structured JSON across 12 read endpoints, with signed webhooks. Build research tools on the same data that powers Flock.

200 OK
GET /v1/disclosures

{
  "items": [
    {
      "id": "f3a9...",
      "entityId": "e1b2...",
      "securityId": "s7c4...",
      "action": "acquired",
      "qty": 250000,
      "filedAt": "2026-05-28T09:14:00Z",
      "sourceType": "nse_bulk",
      "sourceUrl": "https://nseindia.com/...",
      "confidence": 0.98
    }
  ],
  "nextCursor": "eyJpZCI6...",
  "total": 1
}
Read endpoints
12
Webhook event types
4
Typed clients, generated
OpenAPI 3.1
Registers in the corpus
9

Endpoint and register counts as of 20 August 2026.

What's in the API

Entities
canonical investors, funds, FIIs, and 13F filers, with resolved aliases
Disclosures
every ingested filing, time-stamped and source-linked
Holdings
reported holdings per entity
Announcements
corporate announcements per security, filterable by category, with the exchange's own subject string kept in rawCategory
Convergence
multi-entity disclosure overlap as a query primitive — surfaced in the product as Smart Money Overlap
Webhooks
disclosure.created, announcement.created, convergence.created, convergence.updated — the four types registration accepts
Test keys
sk_test_* keys read the same live data as sk_live_* — they are for wiring up an integration, not a fixture dataset
OpenAPI 3.1 spec
generate a typed client in your language instead of writing one

The endpoints

Full request/response shapes in the OpenAPI spec.

  • GET /v1/entities

    Resolved entities — investors, funds, FIIs and 13F filers — cursor-paginated.

  • GET /v1/entities/:id

    One entity, with aliases collapsed onto a single identity.

  • GET /v1/entities/:id/disclosures

    Every disclosure filed by one entity, cursor-paginated.

  • GET /v1/entities/:id/holdings

    Reported holdings for one entity, as disclosed in public filings.

  • GET /v1/securities

    Securities across India and the US, searchable by name or ticker.

  • GET /v1/securities/:id

    One security, with its ISIN and NSE / BSE tickers.

  • GET /v1/securities/:id/disclosures

    Every disclosure that names one security, cursor-paginated.

  • GET /v1/securities/:id/holders

    Entities that have disclosed holdings in one security.

  • GET /v1/securities/:id/announcements

    Corporate announcements for one security, cursor-paginated.

    category-filterable

  • GET /v1/securities/:id/events

    Upcoming exchange calendar dates for one security — board meetings for results, dividends and fund raising.

    not paginated

  • GET /v1/convergence

    Multi-entity disclosure overlap as a query primitive — surfaced in the product as Smart Money Overlap.

  • GET /v1/convergence/:id

    One overlap event: the entity count, the window, and the security involved.

Coverage, pricing and redistribution

What is in the data register by register, how often each feed updates, the plan price, and what you may send on to your own clients — all on one page, with a form that reaches a person.

Flock for business

Build against live data.

A test key reads the same live registers as a live key, so your integration tests assert on real filings. A person issues it the same day your plan is active, and stays reachable afterwards.