Skip to main content
All list endpoints support offset-based pagination via limit and offset query parameters.

​
Parameters

ParameterTypeDefaultDescription
limitinteger25Number of results to return. Max varies by endpoint.
offsetinteger0Number of results to skip before returning data.
include_totalboolean—Pass true to include the total count in the response.
Limits by endpoint:
EndpointMax limit
/api/entities, /api/investors, /api/founders500
/api/transactions, /api/valuations2000

​
Response shape

{
  "data": [ ... ],
  "page": {
    "limit": 25,
    "offset": 0,
    "total": 5634
  }
}
  • page.limit — the applied limit
  • page.offset — the applied offset
  • page.total — total matching records; only present when include_total=true

​
Paging through results

# Page 1 (records 1-25)
curl "https://api-next.dealroom.co/api/entities?sort=-launch_year&limit=25&offset=0" ...

# Page 2 (records 26-50)
curl "https://api-next.dealroom.co/api/entities?sort=-launch_year&limit=25&offset=25" ...

# Page 3 (records 51-75)
curl "https://api-next.dealroom.co/api/entities?sort=-launch_year&limit=25&offset=50" ...

​
Including the total count

By default page.total is omitted. Pass include_total=true to include it: 
curl "https://api-next.dealroom.co/api/entities?sort=-launch_year&limit=25&include_total=true" ...
For large datasets, skip the total count when you don’t need it (e.g. for infinite scroll) — omitting it avoids a full-table count query.
If you need to export large datasets, consider using the aggregate endpoints to summarise data instead of paging through raw entities.