REST API
Programmatic operations
Use the generated API reference for endpoints, payloads, and authentication requirements.
Reference & next steps →Developers · API, webhooks & MCP
Bring Moja into the way you work.
Build against the API. Receive events through webhooks. Use MCP from a compatible assistant to ask focused questions of your Moja data.
Webhooks
Event delivery
Send configured call data to systems that need to react to activity.
Reference & next steps →MCP
Assistant access
MCP is available. Confirm the supported client, account enablement, and current tool scope for your workflow.
Reference & next steps →MCP connection checklist
Connect deliberately.
Endpoint URLs, authentication steps, exact tool names, and client setup change. Their source of truth belongs in the help center—not in a copied marketing-page configuration.
Open the help center →- 01
Client & connection
Confirm your client’s supported transport and connection requirements. Get the current endpoint from the help center or enablement team.
- 02
Identity & permissions
Use authorized account access. Confirm the user or service identity and the data it is permitted to read.
- 03
Enabled tool scope
Review the current tool catalog for your deployment. For reporting-only access, verify the tools cannot perform mutations rather than assuming the client makes them read-only.
- 04
Review & controls
Check result scope and dates. For any enabled action workflow, verify approval, execution, history, and recovery controls before using it.
Questions worth connecting for
Ask about the operation.
Which publishers drove converted calls in the last reporting window?
Where did cost per qualified call change?
Which routes or buyer responses need investigation?
Illustrative questions—not synthetic answers or a guarantee that every query is supported.Read access is still a permission.
Reports can contain sensitive business or caller data. Grant access deliberately, including for analysts and external partners.
Protocol is not a capability guarantee.
The assistant, connection, account permissions, and enabled tool catalog all matter. Do not infer write access—or its absence—from the MCP label alone.