One unified REST API to plug your line-of-business software or your own application into your company’s commercial life: contacts, companies, opportunities, meetings, and webhooks that tell you the moment something changes.
https://api.metaventus.comX-API-KeyJSONFrom the first call to production.
Your first successful call, in three steps.
curl https://api.metaventus.com/v1/entities \ -H "X-API-Key: sk_live_…"Get an API key and sign your requests.
X-API-KeyEvery endpoint, its parameters and its responses.
772 endpointsMove events between Metaventus and your own systems.
{{http.status}}Node.js, Python, PHP and cURL.
fetch() · requests · GuzzlePer-route ceilings and handling 429s.
120 req/minThe API covers eight product areas. Move onto a panel: it unfolds and pushes the others aside.
What you want to know before writing the first line.
In your Metaventus workspace, open Admin center → API keys and create a secret key. It is shown only once, and then travels in the X-API-Key header of every request. Creating keys requires a professional plan.
Read the guide →Yes: a REST API on https://api.metaventus.com, JSON in requests and responses. Results are wrapped in a data field, and lists add a meta object carrying the total, the page and the page size.
Read the guide →A hundred and twenty requests per minute per IP address for reads, ten to thirty for writes, and a global ceiling of a thousand requests per minute. Past that the API answers 429: exponential backoff is enough to get through.
Read the guide →Through automation scenarios, which call your system at the moment of the event — and the other way round, your system starts a scenario by calling Metaventus. Polling the API in a loop is never necessary.
Read the guide →No. A key in a header and JSON both ways: cURL, fetch in Node.js or requests in Python are enough. Ready-to-copy examples are provided for each.
Read the guide →The help center covers the common cases; our team takes it from there.
Help center