The Dividend Registry API

What you get

The same dividend records that power this site: declared amounts with their ex-dividend, record and payment dates, the dividend type, the PID and special flags, and a link to the filing each figure came from. Records are rebuilt daily, after the day’s filings are ingested.

Coverage is FTSE 350 companies and London-listed ETFs — around 780 fund share classes, each checked against its own distribution notices and, for the largest fund families, against the provider’s own published history. A fund is looked up by its London ticker, and any other London line of the same share class returns the same record. The archive runs back to 2015 and is UK-only.

Base URL and authentication

Every request needs your API key in an Authorization header. Keys look like dr_live_… and are shown once, on the page after payment — we keep only a hash, so we cannot show one again.

curl https://api.dividendregistry.com/dividends/company/BP \
  -H "Authorization: Bearer YOUR_API_KEY"

It returns the company’s record — shortened here to its latest dividend and the main fields; the full list follows below:

{
  "kind": "company",
  "ticker": "BP",
  "company": "BP",
  "lei": "213800LH1BZH3DI6G760",
  "ftse_index": "ftse100",
  "upcoming": [],
  "recent": [
    {
      "dividend_type": "quarterly",
      "status": "declared",
      "amount": "8.66000000",
      "currency": "USX",
      "gbp_equivalent": "6.40590000",
      "declaration_date": "2026-08-04",
      "ex_dividend_date": "2026-08-13",
      "record_date": "2026-08-14",
      "payment_date": "2026-09-18",
      "is_pid": false,
      "is_special": false,
      "scrip_available": true,
      "source": {
        "source_doc_url": "https://data.fca.org.uk/artefacts/NSM/RNS/88d5b364-4449-4f63-b89f-d99b483cc312.html",
        "published": "2026-09-08T09:00:01Z",
        "tier": "filing"
      }
    },
    …
  ]
}

Requests are GET only, and responses are JSON. Keep your key out of anything you publish — browser code included, since a key in a web page is a public key.

Endpoints

Which list a dividend is in

upcoming and recent are decided by the ex-dividend date, falling back to the payment date. A dividend that has gone ex but has not been paid yet is therefore in recent, with its cash still to come — if you are showing someone what they are owed, read both lists. A record with neither date appears in neither.

Units and currencies

This is the part to get right, and the one place a careless integration goes wrong by a factor of a hundred.

• amount is per share, in the unit named by currency, exactly as the issuer announced it.
• An ISO code is the major unit — GBP pounds, USD dollars, EUR euros. An ISO code with an X suffix is the sub-unit, one hundredth of the major: GBX pence, USX US cents, EUX euro cents. UK ordinary dividends are overwhelmingly GBX.
• To get pounds: GBX ÷ 100, GBP as-is. Branch on the currency field — never guess from the size of the number.
• gbp_equivalent is the issuer’s own stated sterling figure, in pence — never a rate we calculate. It is null until the issuer announces it: a company declaring in dollars or euros fixes its sterling rate nearer the record date, and gbp_equivalent_announced_date records when. If it is null, there is no sterling figure to use — do not invent an FX rate.

Provenance

Every record carries a source object: the filing id, the stable disclosure id, the URL of the announcement on the national archive, and its publication timestamp in UTC. Nothing is served that cannot be traced to a filing, and records that our rules could not resolve are withheld rather than guessed.

Corrections create a new version rather than overwriting the old one, and only the current version is served. Withdrawn and cancelled dividends are never served.

Status and type values

status is declared or proposed — proposed means a final recommended in results and still subject to approval at the AGM. dividend_type is final, interim, quarterly, monthly, special or other.

Two honest caveats: other is a catch-all where the cadence is not yet resolved, and cadence wording is not fully normalised between issuers — a quarterly payer may appear as quarterly or interim. Treat is_special and is_pid as authoritative for those two attributes rather than reading the type word.

Limits

• 60 requests a minute per key. Over it, you get 429 with a retry-after header.
• A monthly allowance — 10,000 requests on Hobby, 100,000 on Pro. It is a hard stop, not an overage charge: at the limit you get 429 until the allowance resets.
• The allowance resets on your billing date, not the first of the month, and yearly plans still get a monthly allowance. Responses carry x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset.

Errors

Errors return a JSON body of {"detail": "…"} with a matching status: 400 a bad parameter, 401 a missing or invalid key, 402 a payment problem on the subscription (access resumes when payment succeeds), 404 an unknown ticker or month with no data, 405 a method other than GET, and 429 either rate limit.

Freshness

The data is rebuilt once a day, after the evening ingest of that day’s filings, including at weekends — a payment date passing changes what is upcoming even on a day no company files anything. /health reports the date being served.

Before you build

Read the API terms — in particular what the licence does and does not allow you to do with the data. The methodology explains how the registry is compiled, and the disclaimer applies to the API as it does to the site: this is information compiled from filings, not advice, and the issuer’s own announcement is always the authoritative source.

Questions, or a use case that does not fit these plans? [email protected].