---
title: "Upcoming investor-relations events (earnings webcasts, conferences, presentations, shareholder meetings) from the company's IR website, soonest first. Coverage is partial — the coverage block states whether the company's IR page has been discovered and scraped, so an empty list is interpretable. nextEarnings states the next earnings call when one is known: scheduled, or estimated from past call dates."
method: GET
path: "/v1/stocks/{ticker}/ir-events"
tags: ["InvestorRelations"]
---

# Upcoming investor-relations events (earnings webcasts, conferences, presentations, shareholder meetings) from the company's IR website, soonest first. Coverage is partial — the coverage block states whether the company's IR page has been discovered and scraped, so an empty list is interpretable. nextEarnings states the next earnings call when one is known: scheduled, or estimated from past call dates.

`GET /v1/stocks/{ticker}/ir-events`

## Request

- Base URL: `https://api.equibles.com`
- URL: `https://api.equibles.com/v1/stocks/{ticker}/ir-events`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/equibles/apis/equibles-api/docs/v1/stocks/:ticker/ir-events/get.ts> (a function with typed inputs; its response is checked against the schema)

## Path parameters

- `ticker` string, required

## Query parameters

- `limit` integer
- `eventType` string

## Response `200`

OK

- IrEventsResponse
  - `coverage` IrCoverageDto: How far the IR-website pipeline has gotten for the company, so an empty feed is interpretable: a coverage gap is not evidence the company publishes nothing.
    - `status` string, nullable: "scraped" — the IR page's content has been scraped and content has been parsed from it (an empty feed then reflects what the scraper extracted); "sec-filings" — every news item comes from the press releases the company furnished with its 8-K filings, because its IR site has no news feed (news surface only); "attempted" — the page has been scraped but no content has ever been parsed from it, so an empty feed is a coverage gap; "discovered" — the IR page is known but its content has not been scraped yet; "none" — no IR page has been discovered for the company. For "attempted", "discovered" and "none" an empty feed is a coverage gap, not an absence of news or events.
    - `lastScrapedAt` string, date-time, nullable: When the IR content scrapers last pulled the company's news/events (UTC); null unless status is "scraped" or "attempted".
  - `nextEarnings` IrNextEarningsDto: The company's next earnings call as the earnings-call lane knows it, stated whether or not the IR calendar lists it.
    - `date` string, date: Call date (UTC calendar day).
    - `basis` string, nullable: "scheduled" — a call on record for that date; "estimated" — projected from the company's past call dates (the median recent gap after the last call), not announced by the company.
    - `resultsReleaseDate` string, date, nullable: The results-release date the company announced for a scheduled call; null when none was announced, and always null for an estimate.
  - `listingNotice` ListingNotice: What happened to a requested ticker that no longer trades. "delisted": the company has no current US listing, so the answer is its history. "renamed": the company now trades as successorTicker, its current US presentation ticker (possibly another share class). A listed series (short volume, short interest, off-exchange volume, fails-to-deliver, congressional trades) is the retired ticker's own; a company-level read is the company's data.
    - `status` string, nullable: "delisted" or "renamed".
    - `ticker` string, nullable: The retired ticker as listed.
    - `delistedOn` string, date, nullable: The day the retired listing stopped trading, when known.
    - `successorTicker` string, nullable: For "renamed", the company's current US presentation ticker; null for "delisted".
  - `data` IrEventDto[], nullable
    - `startsAt` string, date-time
    - `type` string, nullable
    - `title` string, nullable
    - `url` string, nullable

## Other responses

- `400`: Bad Request
- `404`: Not Found

## Changes

- **2026-11-06** `666e06778588`: 5 info
  - added the new optional `query` request parameter `eventType`
  - added the non-success response with the status `400`
  - added the optional property `error/availableDates` to the response with the `404` status
  - added the optional property `listingNotice` to the response with the `200` status
  - …1 more

[Operation history](https://skmtc.dev/equibles/apis/equibles-api/changes/v1/stocks/:ticker/ir-events/get.md)

---

[API](https://skmtc.dev/equibles/apis/equibles-api.md) - [All operations](https://skmtc.dev/equibles/apis/equibles-api/llms.txt) - [OpenAPI document](https://skmtc.dev/equibles/apis/equibles-api/revisions/713a3e840323?raw)
