Events & quotes
Company events
Section titled “Company events”GET /v1/companies/{companyId}/events?from=2026-01-01&to=2026-12-31&limit=20| Parameter | Type | Required | Rules |
|---|---|---|---|
companyId |
UUID | Yes | Path |
from, to |
ISO date | Yes | YYYY-MM-DD; from ≤ to; span at most 366 days |
limit |
integer | No | 1–20; default 10 |
offset |
integer | No | 0–100; default 0 |
The result includes events with a date in the requested interval or an estimated window that overlaps it.
| Field | Meaning |
|---|---|
id, title, type |
Event identity and category |
event_date, timezone |
Available date and associated timezone |
lifecycle, is_confirmed |
Confirmation state |
window_start, window_end |
Estimated date window when available |
fiscal_period |
Associated reporting period |
source_url |
Available source |
Returned lifecycle values can include confirmed, estimated and awaiting_announcement. Display estimated windows as estimates. Do not turn an expected reporting window into a confirmed announcement date.
Available quote
Section titled “Available quote”GET /v1/companies/{companyId}/quotecompanyId is a required UUID path parameter. This endpoint returns Fisk’s available quote payload for the company, including the source, retrieval time, trading date and freshness information when available.
Quotes can be delayed, historical or unavailable. The endpoint is not a real-time trading feed. Do not use its response as an execution price.
Unavailable quote
Section titled “Unavailable quote”A valid company may have no available quote. The response can succeed with data: null:
{ "data": null, "meta": { "status": "unavailable", "sourceNotes": "No quote is available; do not substitute an estimated price." }}This snippet shows the relevant fields; standard request metadata is also included.
Render “Price unavailable” instead of a zero. Preserve the last trading date and stale status when a historical quote is returned.
Building a research view
Section titled “Building a research view”Place a quote’s date and source beside the price. Keep event confirmations visible in a calendar or upcoming-results panel. Treat these responses as separate datasets: retrieving a recent event does not make a historical quote current.