> ## Documentation Index > Fetch the complete documentation index at: https://docs.nordicfinancialnews.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Calendar Event > Fetches a single scheduled calendar event by ID. Cancelled or discarded events return 404. Responses are cached with `ETag` and `Last-Modified` headers and a `private, max-age=300` `Cache-Control`; clients can send `If-None-Match` to receive a `304 Not Modified`. ## OpenAPI ````yaml https://nordicfinancialnews.com/openapi/v1/openapi.yaml get /api/v1/calendar_events/{public_id} openapi: 3.0.1 info: title: Nordic Financial News API version: v1.0 description: > REST API for Nordic financial news. Each article is summarized in English (headline, short summary, and key points) with the original-language article linked via `article_url`. The full article body stays at the source. ## Authentication All endpoints require Bearer token authentication using an API key. Include the API key in the Authorization header: ``` Authorization: Bearer YOUR_API_KEY ``` ## Rate Limiting The API enforces per-hour rate limits based on your plan: - **Free**: 100 requests/hour - **Pro**: 5,000 requests/hour Rate limit information is included in response headers: - `X-RateLimit-Limit`: Maximum requests per hour - `X-RateLimit-Remaining`: Requests remaining - `X-RateLimit-Reset`: Seconds until limit resets - `X-RateLimit-Policy`: Human-readable rate limit policy (e.g. `5000 per hour; token bucket`) The `/health` endpoint is exempt from rate limiting and does not return rate limit headers. ## Monthly Usage Limits Free and Plus keys have a fixed monthly allowance that resets at the start of each calendar month: - **Free**: 100 requests/month - **Plus**: 100 requests/month Responses on these plans include: - `X-Monthly-Limit`: Maximum requests for the current month - `X-Monthly-Remaining`: Requests remaining this month - `X-Monthly-Reset`: ISO 8601 timestamp when the allowance resets When the allowance is exceeded, the API returns `429 Too Many Requests` with a `Retry-After` header. Pro has no hard limit. It includes 25,000 requests per billing cycle, with usage-based pricing beyond that, so requests are never blocked. Responses on Pro include: - `X-Monthly-Usage`: Requests used in the current billing cycle - `X-Monthly-Reset`: ISO 8601 timestamp when the current billing cycle ends A Pro billing cycle follows your subscription's billing period, which begins on the date you subscribed and is not necessarily a calendar month. Usage is counted by day, so the first day of a billing cycle is counted in full. ## Caching The API supports HTTP caching with ETags. Include the `If-None-Match` header with the ETag from a previous response to receive a 304 Not Modified response if the data hasn't changed. ## Pagination List endpoints support cursor-based pagination. Use the `cursor` parameter with the value from `pagination.next_cursor` in the response to fetch the next page. Paginated responses also include a `Link` header with `rel="next"` pointing to the next page URL. ## Incremental Sync To keep a local copy current, poll `updated_after` — not `published_after`. 1. Request `?updated_after=`. 2. Results are ordered by `updated_at` ascending and cursor-paginated. 3. Follow `pagination.next_cursor`, resending the same `updated_after`, until it is `null`. 4. Only then store the time the sync started, minus a small overlap, as your new watermark. A minute is plenty. Step 3 matters: a response is capped at `limit` (default 25, max 100), so a changed set larger than one page arrives across several. Advancing your watermark before draining every page skips the remainder. The overlap in step 4 matters for the same reason: a record's `updated_at` is set when the write happens, but it only becomes visible when that write commits a moment later. Without an overlap a record can be stamped just before your watermark and land just after it, and you would never ask for it again. Re-reading a minute of changes is cheap and idempotent. `published_at` is editorial time — when the news happened, not when the record reached this API — so a record can appear with a `published_at` older than one you already hold. Records are re-sent when they change, so reconcile by `id`. Removals are not signalled: an article withdrawn from the feed simply stops being returned. Incremental sync tells you what changed, not what disappeared, so treat a local mirror as append-and-update rather than an exact replica. ## Error Handling Errors follow the RFC 9457 Problem Details format with appropriate HTTP status codes. contact: name: API Support email: hello@nordicfinancialnews.com servers: - url: https://nordicfinancialnews.com description: Production server security: [] paths: /api/v1/calendar_events/{public_id}: parameters: - name: public_id in: path required: true description: >- The calendar event ID, as returned in the `id` field of list responses. example: cale_q3volvo1 schema: type: string get: tags: - Calendar Events summary: Get Calendar Event description: >- Fetches a single scheduled calendar event by ID. Cancelled or discarded events return 404. Responses are cached with `ETag` and `Last-Modified` headers and a `private, max-age=300` `Cache-Control`; clients can send `If-None-Match` to receive a `304 Not Modified`. responses: '200': description: Calendar event retrieved content: application/json: examples: earnings_report: value: calendar_event: id: cale_q3volvo1 title: Volvo AB Q3 2026 interim report description: >- Publication of the interim report for Q3 2026 and earnings call at 10:00 CET. event_type: earnings_report status: scheduled date_precision: exact fiscal_period: q3_2026 scheduled_at: '2026-10-22T05:00:00.000Z' timezone: Europe/Stockholm local_time: '2026-10-22T07:00:00.000+02:00' scheduled_at_changed_at: null source_article_id: art_xyz45678 company_id: w55fcw3pbg3p country: SE dividend: null updated_at: '2026-03-01T09:00:00.000Z' schema: type: object required: - calendar_event properties: calendar_event: $ref: '#/components/schemas/CalendarEventDetail' '401': description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/problem_details' '404': description: Calendar event not found content: application/json: examples: not_found: value: type: https://docs.nordicfinancialnews.com/problems/not-found title: Not Found status: 404 detail: The requested resource could not be found instance: urn:request:a1b2c3 schema: $ref: '#/components/schemas/problem_details' security: - bearer_auth: [] components: schemas: CalendarEventDetail: allOf: - $ref: '#/components/schemas/CalendarEventSummary' problem_details: type: object required: - type - title - status - detail - instance properties: type: type: string description: URI that identifies the problem type title: type: string description: Short human-readable summary status: type: integer description: HTTP status code detail: type: string description: Human-readable explanation instance: type: string description: URI that identifies the specific occurrence CalendarEventSummary: type: object required: - id - title - event_type - status - scheduled_at - company_id properties: id: type: string description: Unique calendar event identifier example: cale_q3volvo1 title: type: string description: Event title as reported by the issuer or exchange example: Q3 2026 Interim Report description: type: string nullable: true description: Optional long-form description example: >- Publication of the interim report for Q3 2026 and earnings call at 10:00 CET. event_type: type: string description: The kind of calendar event enum: - earnings_report - earnings_call - agm - egm - dividend - capital_markets_day - trading_update - conference_presentation - ma_announcement - ma_offer_deadline - ma_completion - listing - delisting example: earnings_report status: type: string description: >- Event lifecycle status. `scheduled` is upcoming; `published` means the event has occurred (events flip ~2 days after their date); `cancelled` means the issuer withdrew it. List endpoints return `scheduled` + `published` and exclude `cancelled` by default — pass the `status` query parameter to filter (e.g. `status=cancelled`). enum: - scheduled - published - cancelled example: scheduled date_precision: type: string description: >- Granularity of `scheduled_at`. `exact` = timestamp known; `day` = date only; `month` = only the month is known. Consumers that need a date should still use `scheduled_at` (set to a representative point inside the window). enum: - exact - day - month example: day fiscal_period: type: string nullable: true description: >- Fiscal period slug (required for report-type events, e.g. `q3_2026`, `fy_2025`) example: q3_2026 scheduled_at: type: string format: date-time description: >- Scheduled date/time in UTC (ISO 8601). For the local calendar date use `local_time` instead — a day-precision event is stored at local midnight, so its UTC instant falls on the previous day for ahead-of-UTC (Nordic) zones. example: '2026-10-22T05:00:00.000Z' timezone: type: string description: >- The issuer's IANA timezone, used to interpret `scheduled_at`. Resolved from the source article, falling back to the company's country zone. example: Europe/Stockholm local_time: type: string format: date-time description: >- `scheduled_at` rendered in the issuer's `timezone` (ISO 8601 with offset). Use this for the correct local date/time — its date is right even for day-precision events. example: '2026-10-22T07:00:00.000+02:00' scheduled_at_changed_at: type: string format: date-time nullable: true description: >- When `scheduled_at` last changed. Useful for change-feed consumers tracking date moves. example: '2026-03-15T10:00:00.000Z' source_article_id: type: string nullable: true description: >- ID of the article the event was extracted from. `null` when the source article is not retrievable (not live, or removed). Best-effort: on the free plan it may reference an article your plan can't fetch (premium source or outside the age window). example: art_xyz45678 company_id: type: string description: ID of the company this event relates to example: w55fcw3pbg3p country: type: string nullable: true description: Country ISO 3166-1 alpha-2 code example: SE dividend: type: object nullable: true description: >- Dividend lifecycle dates. `null` for non-dividend events. `scheduled_at` follows the priority ex-date > record-date > payment-date — whichever is explicitly stated. properties: ex_date: type: string nullable: true description: >- Ex-dividend date (YYYY-MM-DD). The market-event anchor — share price drops on this day. example: '2026-04-25' record_date: type: string nullable: true description: >- Record date (YYYY-MM-DD). Holders of record on this date receive the dividend. example: '2026-04-28' payment_date: type: string nullable: true description: >- Payment date (YYYY-MM-DD). When the cash is distributed to shareholders. example: '2026-05-06' declaration_date: type: string nullable: true description: >- Declaration / announcement date (YYYY-MM-DD). Metadata only — never used as the calendar anchor. example: '2026-03-20' kind: type: string enum: - ordinary - special description: >- Tranche type. `ordinary` for the recurring/regular dividend; `special` for an extra/bonus/one-off dividend. When an issuer proposes both for the same date, they are returned as two separate events. example: ordinary updated_at: type: string format: date-time description: >- When the event was last updated (ISO 8601) — use with `updated_after` for polling example: '2026-03-01T09:00:00.000Z' securitySchemes: bearer_auth: type: http scheme: bearer bearerFormat: API Key description: API Key authentication using Bearer token ````