The Best Perfex CRM API & Integration Modules
Perfex CRM ships without a public API, so the moment you need to sync invoices to your accounting tool, feed leads into a marketing platform, or build a mobile app on top of your client data, you need an integration module. The catch is that "connect Perfex to X" can mean four genuinely different things, and the wrong choice means rebuilding later.
The distinction that matters most is direction. A REST or GraphQL API is request-driven: your code asks Perfex for data or writes it back, on demand. A webhook is event-driven: Perfex pushes a notification the instant something happens, with no polling. And a no-code connector like Zapier wraps an API so non-developers can build workflows by clicking, not coding. Pick by who is integrating (developer vs. ops person), which way the data flows, and whether you need to read everything or just react to changes.
The six modules below are the ones worth comparing. All run on the CodeIgniter-based Perfex core and support PHP 7.x and 8.x. They are ordered for the most common need first - a full programmatic surface - down to the more specialised billing-sync case. Where two modules overlap, the notes call out exactly which one fits.
-
This is the default answer to "how do I integrate Perfex" and, at roughly 2,900 sales and a 4.91 rating, the most proven module of the set. It exposes almost the entire CRM - invoices, estimates, proposals, payments, subscriptions, contracts, expenses, customers, leads, projects, milestones, tasks (with checklists and assignees), timesheets, calendar events, tickets and replies, plus generic CRUD against any third-party module's tables - through standard REST verbs and predictable URLs. What lifts it above a plain API is the operational layer around it: per-key access control (you choose Get/Search/Create/Update/Delete per resource, with rate limits, burst allowance and expiry), an events webhook engine with HMAC SHA256 signing and retries, native Zapier/Make.com/n8n connectors plus a Postman collection, a reporting dashboard, and an interactive Swagger/OpenAPI playground. Security middleware adds IP whitelisting (CIDR), request-size limits and security headers, with Bearer, query-param or JWT auth.
Best for: Developers who need full, two-way programmatic access to the whole CRM - and want webhooks, rate limiting and automation connectors in one module rather than buying them separately.
-
Where the REST API gives you a fixed endpoint per resource, this module exposes one GraphQL endpoint over the entire database, so a single query returns exactly the fields you need across several entities - fetching a client together with their recent invoices in one round-trip instead of two. Its standout is reach: it can query every table, field and option in your installation, including entities added by third-party Perfex modules from any author, not just the core CRM. It is not read-only - mutations create, update and delete records by ID, and queries can be constrained by ID and result limits to keep responses lean. The trade-off versus the REST module is scope: this is a focused, typed query layer, without the built-in rate-limiting dashboard, webhook engine and no-code connectors that ship with the REST API.
Best for: Developers who have invested in custom or third-party add-ons and need to read and write those custom-module tables - or who want one precise query instead of many REST calls.
-
If you do not need to pull data - you just need Perfex to tell another system the instant something changes - this is the efficient choice, because webhooks push while an API retrieves, with none of the polling overhead. It attaches outbound HTTP requests to fourteen core areas (leads including conversion and mark-as-lost, customers, invoices and recurring invoices across their full lifecycle, estimates and proposals, tasks, projects, tickets, contracts, calendar events, payments, expenses, staff, custom fields, and credit notes), firing on Create/Update/Delete and lifecycle actions. You shape each request yourself: GET/POST/PUT/PATCH/DELETE, JSON payloads built from the record's fields, 32 built-in headers plus custom ones for authenticating to a third-party API. Operational tooling - delivery logs with response codes, a test-webhook button, clone, and delayed/scheduled triggers (via a separate cron) - makes it production-ready. Note the flagship REST API module already bundles a webhook engine; choose this standalone module when push notifications are all you need.
Best for: Teams who only need Perfex to notify other systems on events (a paid invoice, a new lead) and want event coverage without paying for a full read/write API.
-
This registers Perfex as a native Zapier app, so ops and marketing staff can wire it into 7,000+ services without writing integration code. Triggers fire a Zap when a Lead, Customer, Proposal, Estimate, Invoice, Payment, Contract, Project, Task or Ticket is created; actions let other apps write back into Perfex - creating a Lead, Customer, Proposal, Estimate, Invoice, Contract, Project, Task, Ticket or Timesheet, and finding an existing Customer to avoid duplicates. It also ships an optional documented REST API for developers when a Zap is not enough. The honest framing: if you already run the flagship REST API module, that includes a Zapier connector, so this standalone module is for teams whose primary need is Zapier-driven, no-code automation rather than a full custom API.
Best for: Non-developers who want to automate Perfex against their existing stack through Zapier's visual builder, with no code.
-
The other API modules expose the whole admin-side CRM; this one is deliberately scoped to the Customers Area, so every request is locked to the authenticated customer and only ever returns that client's own records - a controlled window, not a back door into the full CRM. It covers the client lifecycle end to end: token login and registration, projects (with discussions, tabs, and add/update tasks), invoices, estimates with accept/decline, payments and credit notes, proposals and contracts with commenting, tickets including creation and replies, the knowledge base, plus file/attachment endpoints and pagination. Recent versions added customer profile management, so it is no longer read-only. This is the module you build a customer-facing product on, not the one you use for internal back-office automation.
Best for: Anyone building a client-facing app, branded self-service portal or mobile app where each user must see only their own Perfex data.
-
This is not a general API - it is a single-purpose connector for one specific, common problem: billing in WHMCS while managing relationships in Perfex, and watching the two drift apart. It imports customers, contacts and invoices (with line items, taxes, totals, payment modes and original currency preserved) from WHMCS into Perfex, with detailed sync logs recording what was synced, skipped or failed. By design it is a one-way, on-demand or cron-scheduled sync rather than a fragile real-time hook, which keeps server load predictable; you can sync all history, only records after a date, or only new ones, and no core files in either system are modified. Two honest limits stated upfront: only the primary contact syncs for personal (non-company) profiles, and passwords cannot transfer between the two systems, so imported users get a default password to reset.
Best for: Hosting providers, agencies and multi-currency businesses who bill in WHMCS but want unified client and invoice records in Perfex - without coding an integration.
| Module | Platform | Standard | Rating | Best for |
|---|---|---|---|---|
| REST API module for Perfex CRM | CodeIgniter | $59 | ★ 4.91 | Developers who need full, two-way programmatic access to the whole CRM - and want webhooks, rate limiting and automation connectors in one module rather than buying them separately. |
| Perfex GraphQL API | CodeIgniter | $39 | ★ 4.80 | Developers who have invested in custom or third-party add-ons and need to read and write those custom-module tables - or who want one precise query instead of many REST calls. |
| Webhooks Automation Module for Perfex CRM | CodeIgniter | $89 on CC | ★ 4.75 | Teams who only need Perfex to notify other systems on events (a paid invoice, a new lead) and want event coverage without paying for a full read/write API. |
| Zapier module for Perfex CRM | CodeIgniter | $49 | ★ 5.00 | Non-developers who want to automate Perfex against their existing stack through Zapier's visual builder, with no code. |
| Customers REST API | CodeIgniter | $79 on CC | ★ 5.00 | Anyone building a client-facing app, branded self-service portal or mobile app where each user must see only their own Perfex data. |
| WHMCS Connector & Smart Data Synchronization for Perfex CRM | CodeIgniter | $39 | ★ 5.00 | Hosting providers, agencies and multi-currency businesses who bill in WHMCS but want unified client and invoice records in Perfex - without coding an integration. |
The verdict
For most teams the REST API module for Perfex CRM is the right first purchase: it covers nearly the entire CRM both ways, and folds in webhooks, per-key rate limiting, a reporting dashboard and Zapier/Make/n8n connectors that you would otherwise assemble from separate modules - which is reflected in its ~2,900 sales and 4.91 rating. Reach for the GraphQL API when you need to query third-party custom-module tables or want lean single-request reads; the standalone Webhooks module when you only need event push and no read/write API; and the Zapier module when the people doing the integrating are ops or marketing staff rather than developers. The Customers REST API is the one to build a client-facing app or portal on, and the WHMCS Connector solves the narrow but common job of keeping WHMCS billing and Perfex relationships in sync. Match the module to the direction your data needs to flow and who is wiring it up, and you will not have to redo the integration later.
Questions, answered
REST or GraphQL for Perfex - which API should I choose?
Choose the REST API module for the broadest, most proven surface (it covers nearly the whole CRM and bundles webhooks, rate limiting, a dashboard and Zapier/Make/n8n connectors). Choose the GraphQL API when you need to query third-party custom-module tables that the core does not expose, or when you want one precise query that returns related records in a single round-trip instead of several REST calls. Teams that need both reach and tooling sometimes run them side by side.
What is the difference between a webhook and a REST API here?
A REST API is request-driven and two-way: your code asks Perfex for data or writes it back, on demand. A webhook is event-driven and one-way: Perfex pushes a notification the moment an event happens, with no polling. Use the API to retrieve and manipulate data; use webhooks when you only need Perfex to notify another system that something occurred. The flagship REST API module includes a webhook engine, so you only need the standalone Webhooks module if push notifications are your sole requirement.
Do I need to be a developer to integrate Perfex CRM?
No. The Zapier module registers Perfex as a native app on Zapier, so you can build no-code workflows against 7,000+ services by clicking, not coding. The WHMCS Connector is also configuration-only - add a WHMCS API key and choose what to sync. The REST API, GraphQL API and Customers REST API modules are built for developers and assume familiarity with HTTP/API concepts.
Can these modules access data from my other Perfex add-ons?
Yes, two of them. The REST API module includes generic CRUD against any third-party module's tables, and the GraphQL API is specifically built to query every table and field in your installation, including entities added by modules from any author - not just the core CRM. If reaching custom-module data is your main goal, the GraphQL API is the most direct fit.
Browse the full Themesic catalogue
Every module sold direct - lifetime updates, real developer support, and full source code. Cheaper than the marketplace, with no middleman cut.