NewsIpster raises capital in first pre-seed round

Start with Ipster today

Ipster answers questions, requests and appointments directly through your connected system. 24/7 availability for your business.

Schedule a demoBook a demo
Log inBecome a partner
NLENDE

Developers

Connect Ipster to your own systems.

Manage agents, retrieve conversations and receive every conversation straight in your CRM or automation. With a REST API, webhooks and an MCP connector, fully under your control.

Book a demoContact us
After every conversation200
POST/webhook
{
"event": "call_ended",
"agent_id": "agent_01",
"transcript": "…",
"post_call": {
"sentiment": "positief"
}
}
Building blocks

Everything you need to connect

An API for what you want to control yourself, webhooks for what Ipster passes on to you.

REST API in JSON

Manage Ipster from your own system or script. View and configure agents, retrieve conversations with transcripts, start outbound calls and follow up on tasks. Requests and responses are JSON.

API keys with permissions

Create keys yourself and choose read and/or write per area. If you like, limit a key to your own server with an IP allowlist.

Event webhook

Receive a message when a conversation starts or ends, with the transcript and the result of the analysis. Update your CRM right away or alert your team.

Inbound webhook

Called when a call comes in, before the caller hears the agent. Pass on customer data, pick a different agent or transfer straight away.

Caller lookup

When your phone system or CRM asks for a caller's latest conversation, Ipster returns the summary. Handy for a screen pop-up.

MCP for AI assistants

Work with Ipster from Claude, ChatGPT or another assistant. You decide what the assistant may do: read only, read and propose, or full access.

How to start

From key to first request

  1. 1

    Create an API key

    In the app, go to Organisation, API keys and choose the REST API type.

  2. 2

    Choose the permissions

    Give the key only what it needs and, if you like, limit it to your own server.

  3. 3

    Read the documentation

    You will find all endpoints, parameters and examples in the app under API Docs, once you are logged in.

Documentation

API DocsIn the app, after logging in

You need an Ipster account. You set up a webhook per agent, under Webhook.

Want to know first whether it fits your systems? Get in touch and we will think along.

Prefer to work from an AI assistant? Read about Ipster in your AI assistant.
Secure and in control

You decide who can access what

Permissions per area

Agents, conversations, phone numbers, knowledge bases and tasks, each with read and write.

IP allowlist

Make a key work only from the addresses you specify.

Key shown only once

You see a new key just once, so store it safely.

Revoke it yourself

A key you no longer use, you revoke yourself from the same list.

Within your own organisation

A key belongs to an organisation and only sees what is inside it and in the customers below it.

Privacy filter in webhooks too

If the privacy filter is on, sensitive data is also masked in outgoing webhooks.

Secure your own endpoint with a secret in the URL or an extra header. Ipster does not send any credentials itself.

Questions about an integration?

Tell us what you want to connect and we will work out together what works best.

Contact usBook a demo

Frequently asked questions

About the API, webhooks and MCP

In the app under API Docs, once you are logged in. It lists all endpoints, parameters and examples.

Three. The event webhook reports that a conversation has started or ended. The inbound webhook is called when a call comes in, before the agent picks up. With the caller lookup webhook, your own system asks for a caller's latest conversation details. You set them up per agent.

Yes. With the event webhook you define the JSON structure yourself with a custom payload and you can set extra headers. Without changes, Ipster sends a fixed default payload with, among other things, the transcript and the analysis after the conversation.

With the inbound webhook, Ipster waits a maximum of 10 seconds and retries up to three times on connection errors. If your system is too late, the conversation simply starts without that data. With the event webhook, Ipster retries on temporary errors.

Yes, via the MCP connector. You log in with your own account and choose what the assistant may do. For environments without a login screen, such as n8n, you create a key of the type For AI assistants (MCP).

We use cookies to improve the user experience, analyse website traffic and deliver personalised content. Read our cookie policy.