Developers · Get started
Connect meruma to your systems and your AI
The meruma REST API, webhooks, no-code apps and AI over MCP. Everything you need to connect meruma to your tools.
Three ways in
- The API and webhooks. REST and OAuth 2 for your systems, with signed events when something changes. It is what n8n, Zapier and Make use. Start with Authentication.
- Your own AI, over MCP. Connect Claude, ChatGPT or another AI to meruma: it searches, reads and takes notes as you, with your permissions. Go to Connect your AI.
- Uma, inside meruma. The team’s assistant is already in the app: it answers, looks things up and prepares changes, with nothing to connect. The help center explains it.
What you can do with the API
- Contacts: read and create them, with “create or update” by email or phone so nothing is duplicated.
- Cards: create them, move them between stages, and set tags and amounts.
- Notes: read and add notes on contacts and cards.
- Real-time events: a webhook whenever a contact or a card is created or changes.
The API is included in every plan. Every route lives under https://api.meruma.app/v1, and the API reference has each endpoint with its parameters and examples.
Your first request
- In meruma, go to Integrations › For developers › Create app. Pick the permissions and copy the app’s ID and secret. Anyone whose role includes Integrations can create it.
- Request a token with the ID and secret. It lasts one hour.
- Send it in the
Authorizationheader of every request.
# 1. The token
curl -u "$CLIENT_ID:$CLIENT_SECRET" \
-d grant_type=client_credentials \
https://api.meruma.app/oauth/token
# 2. Who you are: the organization, the app and its permissions
curl https://api.meruma.app/v1/me \
-H "Authorization: Bearer $ACCESS_TOKEN"
Where to go next
- Authentication: the two ways to connect, and the permissions.
- Limits and errors: how many requests you can make and how to read an error.
- Webhooks: the five events and how they arrive.
- n8n: connect without writing code.
Reviewed on