REST API Plugin for RISE CRM

About REST API Plugin for RISE CRM

Connect RISE CRM to anything - REST API, AI agents and webhooks

RISE CRM API plugin: a REST API with 322 documented endpoints, an opt-in MCP server for AI assistants, signed webhooks and n8n, Zapier and Make triggers. Instead of being limited to the RISE web interface, your developers can read and write CRM data programmatically - syncing records, triggering actions and pulling information on demand from any external app, automation tool or custom integration you build.

The RISE API operates over HTTPS and uses JSON as its data format. It is a true RESTful service: standard HTTP methods such as GET and POST issue the requests, and HTTP status codes describe the responses, which keeps it predictable for anyone who has worked with a modern API.

Secure, key-based access

Access is controlled with API keys you generate and manage inside RISE, so every integration authenticates cleanly and you stay in control of who can reach your data. The API management screen itself is restricted to administrators, and as of 2.1.0 sensitive information is kept out of responses - password hashes, payment gateway credentials and staff personal data such as SSN or salary fields are not exposed through the API. A typical request and its JSON response looks like this:

Complete documentation and developer tooling

This is a complete API service for RISE installations, supplied with full online documentation so you can wire up your own third-party connections. Every endpoint group is documented with its available actions and example responses, across 322 documented endpoints in 54 groups, with deep-linkable sections and ready-to-copy code examples in cURL, PHP, Python and JavaScript.

Machine-readable specs and live tooling let you explore the API before writing a line of code:

• OpenAPI 3.0 specification at /api/openapi.json, served straight from your own installation
• Postman collection at /api/postman.json
• Swagger UI at /api/swagger
• An interactive Playground at /api/playground

Two of those live outside your installation as well, so a developer can judge the API before anything is bought:

• An n8n community node, n8n-nodes-rise-crm, published on npm and installable from n8n’s Community Nodes screen - RISE CRM becomes a first-class node on the canvas instead of a stack of hand-rolled HTTP calls.
• A public code-examples repository, github.com/themesic/rise-rest-api-examples, with ready-to-run snippets in cURL, PHP, Python and JavaScript, plus importable copies of the Postman collection and the OpenAPI specification.

If you are unsure about your coding skills or are not certain what an API is, you may want to bring in a developer to handle the integration.

Let AI assistants operate your CRM

A built-in MCP server (Model Context Protocol, JSON-RPC 2.0) is exposed at /api/mcp, so AI assistants can work with your CRM directly instead of you copying data back and forth between tools. It publishes over 200 tools across 40+ resources and supports tools/list, tools/call, resources and prompts.

• Works with Claude, ChatGPT, Cursor and the n8n AI Agent
• Every tool is permission-filtered, so an assistant only reaches what it is allowed to reach
• Opt-in by design: the MCP server is disabled by default and switched on from the API settings screen

Webhooks, batching and automation triggers

Webhooks that push changes to you

Instead of polling for changes, register webhooks and let RISE notify your systems the moment something happens. You can create, list, update, delete and toggle webhooks over the API and subscribe to a full event catalogue with created, updated and deleted events per resource.

• HMAC-SHA256 signed delivery, so your endpoint can verify every payload it receives
• Per-webhook delivery logs for auditing and debugging
• Queued delivery with retries - a slow or failing endpoint never blocks your CRM

Ready-made triggers for n8n, Zapier and Make

Dedicated automation endpoints make RISE a first-class citizen in no-code platforms: discover which resources can be polled, fetch a sample record to map fields against, then poll for anything created or updated since a given timestamp.

Batch requests

A batch endpoint runs many operations in a single request, so bulk imports and multi-step syncs do not turn into hundreds of round trips.

Broad coverage across the whole CRM

The plugin is not limited to a handful of endpoints - it covers the day-to-day objects you actually automate. For most entities you get the full set of operations: create, list, search, update and delete, with documented get-by-ID lookups on many of them.

Sales and clients

• Leads, Clients and Contacts (add, delete, list, search, update; get contact by ID)
• Proposals and Estimates, with their comment threads
• Estimate Requests
• Orders, Contracts and Subscriptions

Projects and work

• Projects, Tasks and Milestones
• Project Comments, Project Members and Timesheets (log time)
• Task checklists, plus checklist templates and groups - apply a group to a task
• ToDo items, Events and Announcements

Billing and finance

• Invoices (add, edit, delete, list, search) and Invoice Payments
• Line items on invoices, estimates, proposals, orders, contracts and subscriptions
• Items and Item Categories
• Expenses and Expense Categories
• Taxes and Payment Methods

Support and communication

• Tickets and Ticket Comments
• Knowledge Base articles and categories, including marking an article helpful or unhelpful
• Messages (including mark as read), Notes and Notifications (including mark as read)

Team and HR

• Users, Teams and team members
• Attendance and Leave Applications
• Read-only staff Roles

Files and templates

• Files for a project, client or task - metadata, folders, categories, download and delete
• Read-only email, ticket, contract and proposal templates

Configuration and auditing

• Custom field definitions, and custom field values on any record
• Labels, filtered by context, with get-by-ID
• Read-only Activity Logs - list, search and get by ID

Line items on sales documents

You can create an invoice, estimate, proposal or order together with its lines in a single call and let the totals calculate themselves, by sending an items array straight to the create or update request. Lines can also be managed on their own: list the lines of an invoice, estimate, proposal, order, contract or subscription, add a line, replace all lines with the totals recalculated, or delete one.

Reporting endpoints

Reporting endpoints return the numbers you would otherwise assemble by hand: summary counts for clients, leads, projects, tickets and invoices, invoiced versus paid versus outstanding over a date range, and project throughput alongside logged timesheet hours.

Helper lookups

Alongside the main resources, a set of miscellaneous read endpoints returns the reference data you need to build correct requests:

• Client groups and contacts by client ID
• Invoice labels and invoice taxes
• Project labels, project members and staff owner
• Ticket labels and ticket types

Typical use cases

Push new leads from your website or landing pages straight into RISE, keep clients and invoices in sync with an external accounting system, log billable time from a separate app, surface tickets in another helpdesk, or build fully custom dashboards on top of your CRM data. Fire a webhook into your own service the moment an invoice is paid or a ticket is opened, wire RISE into an n8n, Zapier or Make workflow without writing code, or point an AI assistant at the MCP server and let it draft an estimate, chase outstanding invoices or summarise this month’s project hours. Anything you can do by hand in RISE becomes something you can automate.

Setup and requirements

This module is built for RISE CRM and takes only a few seconds to install, activate and have a fully working API. Because RISE runs on CodeIgniter, some server configurations require /index.php/ to be included in your API endpoint URLs - the documentation covers this. Once activated it works with your existing RISE CRM data immediately, and the newer surfaces stay out of the way until you want them: the MCP server ships disabled and is enabled from the API settings screen, which only administrators can open.