---
title: "REST API — funding, acquisitions, and exec-move signals | Datahyena"
url: https://datahyena.com/api/
description: "Datahyena"
---

REST API
One envelope, every signal

# Company-event signals on a clean REST API.

Six endpoints, one response shape, cursor pagination. Query funding rounds, acquisitions,
 and executive moves — already deduplicated and resolved to canonical entities. Drop it in
 without writing a parser.

 [Get your API key

→](https://app.datahyena.com/register) [Read the API docs](https://datahyena.com/docs/api-reference)

50 free credits · no credit card required

 datahyena · funding-events
api-request.js
GET /v1/funding-events?limit=1

```
const res = await fetch(
 "https://api.datahyena.com/v1/funding-events?limit=1",
 { headers: { "X-API-Key": process.env.DATAHYENA_KEY } }
);
const { data } = await res.json();
```

Click to run a live sample →

response.json
Waiting for request…

Why the API

## Built to drop in, not to babysit.

The hard parts — sources, deduplication, entity resolution — are already done. You get a
 predictable, typed feed behind a single key.

 One envelope

### The same shape on every endpoint

 success, data, pagination, and meta in identical positions on every response. Write one parser and reuse it across funding, acquisitions, exec moves, companies, and investors.

 success · data · pagination · meta

 Resolved, not raw

### Canonical entities, deduplicated

 Every record is resolved to a canonical company and investors and deduplicated across every outlet that reported it, with the source list attached. No scraping, no cleanup on your side.

 entity-resolved · deduped

 Predictable metering

### Cursor pagination, credits you can see

 Stable cursor pagination and one credit per record returned, reported in the meta of every response. No surprise bills, no offset drift on a live feed.

 cursor paging · 1 credit / record

## Six endpoints, one feed.

Every endpoint is a GET with the same filters, the same cursor pagination, and the same
 envelope. Authenticate with a single `X-API-Key` header.

 ` GET /v1/funding-events ` New funding rounds — company, investors, amount, round. Filter by round, amount, country, industry, vertical (AI, fintech, and more), employee size, or date.

 ` GET /v1/acquisitions ` Mergers and acquisitions with acquirer, target, deal value, and payment type.

 ` GET /v1/exec-moves ` Executive appointments, promotions, and departures with person, company, role, and seniority.

 ` GET /v1/companies ` Canonical company records. Search by name, domain, country, industry, employee bucket, or founded year.

 ` GET /v1/investors ` Canonical investor records. Search by name, type, country, or domain.

 ` GET /v1/companies/timeline ` One company's full timeline: funding, acquisitions, and executive moves, plus firmographics and investors. Resolve by id, domain, name, or LinkedIn URL.

## What teams build with it.

### Enrich your CRM

 Pull fresh rounds for accounts you track and write amount, investors, and round straight onto the company record.

### Trigger outbound

 Poll for new Series A/B in your ICP each morning and route them into sequences before the rest of the market notices.

### Power a dashboard

 Back an internal market-map or portfolio monitor with a feed that is already deduplicated and entity-resolved.

## The API, answered.

 The essentials before your first call.

 How do I authenticate? A single API key in the X-API-Key header. Generate it from the dashboard, and start with 50 free credits — no credit card required.
 How does pagination work? Cursor pagination. Every list response includes a pagination object with the next cursor; pass it back to page forward through a live feed without offset drift.
 How is usage metered? One credit per record returned, reported in the meta of every response so you always know what a call cost. Filtered queries only spend credits on records you actually receive.
 What does a record look like? Each record is resolved to a canonical company and investors, deduplicated across every source that reported it, with the list of sources attached. The full field reference lives in the docs.
 Do you have SDKs? The API is plain REST over HTTPS, so it works with any HTTP client — curl, fetch, requests, or your existing stack. No SDK to install or keep up to date.
 Is there an OpenAPI spec? Yes. The full reference, including every filter and the response envelope, is published in the docs and as an OpenAPI document you can generate clients from.

## Start pulling signals in minutes.

Create a key, claim your 50 free credits, and make your first request today. No sales call,
 no credit card.

 [Get your API key

→](https://app.datahyena.com/register) [Read the docs](https://datahyena.com/docs)

50 free credits · no credit card