---
title: "IPOs in registration and IPOs that have just priced"
method: GET
path: "/intel/offerings/ipo-pipeline"
tags: ["equities"]
---

# IPOs in registration and IPOs that have just priced

`GET /intel/offerings/ipo-pipeline`

## Request

- Base URL: `https://kresmion.com/v1`
- URL: `https://kresmion.com/v1/intel/offerings/ipo-pipeline`
- Auth: HTTP bearer

What is queued and what has just priced, ONE ROW PER DEAL rather than per filing. `data` is the deals still in registration; `meta.recently_priced` is the ones that priced inside the trailing 90 days and `meta.counts` gives the four headline numbers.

A PRICE RANGE IS REPORTED AS A RANGE. What an S-1 or S-1/A states is a low and a high, and neither this route nor the page behind it collapses that to a midpoint.

`recently_priced` deliberately carries NO performance fields: first-day and since-IPO returns stay on the sign-in-only surface, because a /v1 mirror that quietly widened the payload would make that gate meaningless.

`counts.withdrawn_90d` counts withdrawals this lane could attribute to an IPO registration it had already listed. A withdrawal whose original registration was never listed has no known type and is reported separately as `withdrawn_unattributed_90d`, so the narrower number is visibly a subset rather than silently lossy.

## Query parameters

- `tier` string: exchange | otc | unknown | all
- `min_proceeds` number, nullable: Minimum stated gross proceeds. Rows whose proceeds the document never stated are EXCLUDED when this is set.

## Headers

- `authorization` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

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