For Agents
List malma.ai workspace agents and create new leads inside a workspace. Used by automation workflows that hand qualified leads off from a website, form, or chat experience to a malma agent.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the malma Workspace API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with malma Workspace API.
List every agent configured in a malma workspace with their IDs and metadata
Create a new lead in a workspace and route it to a chosen agent
Pass enrichment fields on the lead so the malma agent can personalise outreach
GET STARTED
Use for: I need to push a new lead to a malma workspace from a webform, List all agents in the malma workspace, Create a lead and route it to a specific malma agent ID, Find the agent ID for the SDR malma persona
Not supported: Does not handle outbound calling, agent training, or workspace administration — use for listing workspace agents and creating leads only.
Jentic publishes the only available OpenAPI specification for malma Workspace API, keeping it validated and agent-ready. The malma Workspace API is the official surface for the Make.com and Zapier integrations with malma.ai. It provides two workspace-scoped endpoints: list the agents available in a workspace and create a new lead inside it. Authentication uses a bearer token tied to the workspace.
Drive the lead-creation step from a Make.com or Zapier scenario
Look up workspace agent IDs to validate downstream automation configuration
Patterns agents use malma Workspace API for, with concrete tasks.
★ Webform-to-Malma Lead Handoff
Marketing teams that capture leads on a website want them to reach a malma.ai voice or chat agent immediately. The malma create-lead endpoint accepts the lead's contact and enrichment fields plus the target agent ID, so a webform handler can POST the lead the moment the form is submitted. The agent then picks up outreach without any human in the loop.
POST /workspace/create-lead with the form fields and the target SDR agent ID, then verify the lead lands in the workspace.
Make.com or Zapier Workflow
The malma API is built for no-code automation tools. A Make.com or Zapier scenario can list the workspace agents to populate a dropdown for non-technical users, then create the lead against the selected agent on a downstream trigger. This is the canonical integration path for the malma platform.
GET /workspace/agents to populate the dropdown, then POST /workspace/create-lead with the user-selected agent ID and the trigger payload.
Chat-Qualified Prospect Routing
Live chat tools that qualify visitors can hand off the qualified prospect to a malma voice or chat agent for follow-up. The create-lead endpoint accepts the qualification metadata as part of the lead body so the malma agent picks up the conversation with full context.
On chat qualification, POST /workspace/create-lead with the conversation summary in the lead's enrichment fields and the SDR agent ID.
AI Agent Lead Generation Loop
Outbound and inbound agents can generate leads in malma as part of a wider workflow. Through Jentic the agent searches by intent, loads the schema, and executes the create-lead call while the workspace bearer token stays in the vault. The narrow API surface makes it ideal for agent-as-tool patterns.
Use Jentic to search 'create malma lead', execute POST /workspace/create-lead with the resolved contact and target agent, and return the new lead ID.
2 endpoints — jentic publishes the only available openapi specification for malma workspace api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/workspace/agents
Get workspace agents
/workspace/create-lead
Create lead
/workspace/agents
Get workspace agents
/workspace/create-lead
Create lead
Three things that make agents converge on Jentic-routed access.
Credential isolation
The malma workspace bearer token is stored encrypted in the Jentic vault. Agents call the API through a scoped execution token and Jentic attaches the Authorization header server-side, so the bearer never enters agent context.
Intent-based discovery
Agents search by intent (e.g., 'create malma lead' or 'list workspace agents') and Jentic returns the exact endpoint with its input schema — useful even on a 2-endpoint surface for agent-driven routing.
Time to first call
Direct malma integration: a couple of hours including auth wiring and Make.com plumbing. Through Jentic: minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using malma Workspace API through Jentic.
Why is there no official OpenAPI spec for malma Workspace API?
malma does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call malma Workspace API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the malma Workspace API use?
malma uses HTTP bearer authentication scoped to a workspace. Through Jentic the bearer token is stored encrypted in the vault and attached at execute time, so the agent never sees the raw token.
Can I create a lead through the API?
Yes. POST /workspace/create-lead with the contact details and the target agent ID. The agent picks up the lead inside the workspace once the call returns.
How do I find the right agent ID to route a lead to?
Call GET /workspace/agents to list every agent in the workspace, then pick the agent whose name or persona matches the routing rule for the lead.
What are the rate limits for the malma Workspace API?
Rate limits are not declared in the OpenAPI spec — they depend on the malma plan attached to the workspace. Check the malma.ai dashboard before sending high-volume lead bursts.
How do I create a lead through Jentic?
Run pip install jentic, search 'create malma lead', load the schema for POST /workspace/create-lead, and execute with the contact details and target agent ID. Jentic injects the bearer token from the encrypted vault.