What is the Mergr API?
The Mergr API gives your applications live, read-only access to the same verified records that power mergr.com — private equity firms, companies, M&A transactions, advisors, and professionals — as clean JSON over REST.
It's built for teams that need Mergr data inside their own systems: enriching a CRM, powering an internal dashboard, feeding a deal-sourcing pipeline, or keeping a market map current. If you just need the data in hand (a list, a one-time pull, a recurring file), a custom export is usually the faster path — no code required.
What data does it cover?
Resource | What you can do |
Investors (PE firms) | Retrieve a firm's profile; search firms by type, size, sector interests, geography, activity, and more; pull a matched set's deals, portfolio companies, team, or advisors |
Companies | Retrieve a company's profile and ownership; search by sector, location, ownership status; pull a matched set's investors, acquirers, deals, or advisors |
Transactions | Retrieve deal records; search by deal type, date, size, sector, geography; pull the firms, companies, and advisors involved |
Advisors | Retrieve investment banks and law firms, with deal statistics |
Professionals | Retrieve individual profiles with role and firm affiliation |
Filters | Look up the valid values for search filters (industries, regions, deal types, etc.) |
Search endpoints accept the same filters you see on mergr.com's search screens, so anything you can scope in the interface, you can scope through the API.
How do I get access?
API access is licensed separately from a Mergr membership and is activated per engagement — there are no self-serve tiers or public keys.
Tell us the use case. Contact us with what you're building and roughly how much data it needs.
We scope it. We'll confirm what's available, agree rate limits up front, and quote it — priced to the data and volume.
We activate your key. You receive an API key and secret, plus a short setup guide for your developers.
The basics (for your developers)
Base URL: https://mergr.com/api/v1
Note the base URL itself isn't a browsable page — visiting it directly returns a 404. Requests go to full endpoint paths like /api/v1/authenticate or /api/v1/investor/search.
Authentication — exchange your key and secret for a short-lived token (valid 10 hours), then send it as a header on every request:
GET /api/v1/authenticate?access_key=YOUR_KEY&secret=YOUR_SECRET → { "token": "abc123…", "expires": 1768660000 } GET /api/v1/investor/search?location_state=TX&active_investor=1 Header: X-Auth-Token: abc123…Responses are JSON. Pagination uses skip and limit parameters (25 results per page by default). Rate limits are per-account, daily and monthly, set when your access is scoped — you'll get a 429 response if exceeded.
Example — retrieve one firm:
GET /api/v1/investor?id=1045 Header: X-Auth-Token: abc123…
Returns the firm's profile: name, description, assets, location, sector interests, and more.
Frequently asked questions
Is the API included in my Mergr membership?
No — it's a separate data license. Membership covers the mergr.com interface; the API covers programmatic access for your applications.
Can I get the entire database?
Bulk and full-universe needs are usually better served by a custom export — one file, no integration work. The API is for live, query-based access.
Do you support webhooks or push feeds?
Not currently — the API is pull-based REST. Many teams poll on a schedule; for scheduled deliveries, ask about recurring exports.
Where do I ask a technical question?
Email support@mergr.com.