API Documentation
← All tools
GET/api/v1/regulatory/catalysts

Regulatory Catalysts

regulatory-approvalsAvailable on Free

Returns upcoming regulatory catalyst events (patent expiries, exclusivity expiries, approvals) with per-type counts, the applied filters, and a generation timestamp. Call it to find scheduled regulatory milestones for a company or drug, filtered by sponsor, indication, drug names, LEI, or ticker. Requires at least one of sponsor, indication, drugNames, lei, or ticker; returns 400 if none is supplied or parameters are invalid, and 500 on failure.

When to use it

  • Find upcoming patent and exclusivity expiries for a drug
  • Look up regulatory catalysts for a company by ticker or LEI
  • List approval events expected for an indication

Getting started

Base URL

https://app.caelrith.com/api/v1/tools

Authentication

Include your API key in the x-api-key header.

Rate limit

Every call counts against your workspace’s daily quota for regulatory-catalysts. Exceeding it returns HTTP 429.

Plans and daily limits

PlanAvailableCalls / day
freeyes10
proyes200
custom (default)yes10,000

Plan defaults. A custom workspace may carry per-tenant overrides.

Parameters

Query parameters

ParameterTypeRequiredDescription
sponsorstringNoCompany or organization name sponsoring the drug.
indicationstringNoDisease or therapeutic indication to match.
drugNamesstringNoDrug name or names to match.
windowDaysintegerNoRange 1-3650; default 365 (range 1-3650; default 365)
Range: 1 to 3650
limitintegerNoRange 1-500; default 100 (range 1-500; default 100)
Range: 1 to 500
leistringNoLegal Entity Identifier of the company.
tickerstringNoStock ticker symbol of the company.

Example request

curl -H "x-api-key: YOUR_API_KEY" \
  "https://app.caelrith.com/api/v1/regulatory/catalysts"

Response envelope

Successful responses wrap the payload in a success flag.

{
  "success": true,
  "data": { /* payload */ },
  "meta": { /* pagination, totals */ }
}

Response shape

List responseCATALYSTS

Payload: data.events — Catalyst Events

Counts: data.counts

Common row fields

FieldDescription
trade_nameTrade Name
typeType
event_dateDate
days_to_eventDays
drug_nameDrug
patent_noPatent
exclusivity_codeExclusivity
exclusivity_description—

Empty results: No matching rows (HTTP 200) (also the response when a sponsor / indication / drugNames value cannot be resolved to any graph entity - HTTP 200 with an empty events list, never an error)

Dated catalyst events within +/- windowDays of today: FUTURE patent and exclusivity expiries plus RECENT approvals (approvals look back windowDays; expiries look forward). events are deduplicated by drug+type+date, sorted ascending by event_date and capped at limit (default 100) - the EXACT TOTAL line is the returned (capped) event count, never a graph total. data.counts splits the RETURNED events by type. Each event carries direct sponsor objects plus the direct->ultimate sponsors_chain with canonical LEI/ROR ids. An event's approval_id is an INTERNAL graph key (regulatory_approval/<key>) - it is NOT the public approval_id and must not be fed to the regulatory-approvals tools. Providing more than one of sponsor / lei / ticker is rejected server-side; an unresolvable filter value returns an empty events list (HTTP 200) - verify the exact name and check the echoed filters.

Catalog version mcp-2026-10-28 · generated from the live MCP catalog