mHelpDesk API

Overview

mHelpDesk is a field service management platform for cleaning businesses, HVAC contractors, handyman services, and other residential service providers. It handles job scheduling, customer records, technician dispatch, work orders, invoicing, and customer communication from a single interface. Its straightforward feature set and positioning as an accessible management platform for growing service businesses gives it adoption among cleaning franchises and independent HVAC and handyman operators, making it an integration target for CRM platforms, accounting automation tools, and AI-powered scheduling products targeting these segments.

mHelpDesk does offer a REST API with documented read access to job and customer records. In practice, the read-only boundary is the primary constraint. Write operations, creating jobs, updating job status, managing customer records, and modifying the dispatch schedule, are all unavailable through the API. For teams building a two-way sync between mHelpDesk and an external system, this means the API can pull data out but cannot push anything back. A cleaning business platform that needs to create new jobs from inbound bookings, an AI dispatcher that needs to update status as technicians complete work, or an HR tool that needs to modify the schedule all hit the write-access wall immediately.

Integuru generates a production-ready HTTP API for mHelpDesk using direct HTTP requests against the same endpoints the mHelpDesk web application uses internally. This covers both the read operations the REST API exposes and the write operations and scheduling modifications it does not. The Production plan includes 24/7 on-call maintenance so authentication changes and endpoint updates are resolved before they affect your calls.

Beyond read-only. mHelpDesk's REST API and its web application are separate surfaces with different coverage. Integuru works at the web application layer, using the same authenticated HTTP requests the browser sends when a dispatcher creates a job or a technician marks a visit complete. Write operations, schedule modifications, and the full customer record lifecycle are as accessible through Integuru as any read endpoint. The read-only restriction does not apply.

Why Teams Need This Integration

The gap between the read-only REST API and the full mHelpDesk platform creates specific blockers for teams building on mHelpDesk data.

CRM platforms syncing customer and job data. list_customers and get_customer_detail give CRM platforms a live view of every mHelpDesk customer with contact details, service address, and linked job history. The REST API covers the read side, but CRM connectors that need bidirectional sync, pushing new leads into mHelpDesk as customer records and pulling job history back, cannot reach the write operations through the official channel. create_job is a write operation the REST API does not expose, which means CRM tools that need to push inbound bookings into mHelpDesk have no official programmatic path.

Accounting and invoicing automation products. list_invoices and get_invoice_detail are the core actions for accounting sync pipelines connecting mHelpDesk to QuickBooks, Xero, or a custom billing system. The REST API does not document invoice endpoints as a supported read surface, which means accounting connectors cannot access the invoicing data mHelpDesk generates for every completed job through any official programmatic path. Integuru's direct HTTP layer reaches the invoice surface the web application exposes.

AI-powered scheduling and dispatch tools. get_schedule, create_job, and update_job_status cover the dispatch loop that AI schedulers need for cleaning and handyman operations. An AI tool that routes inbound cleaning bookings, assigns technicians based on proximity and availability, or marks jobs complete from field notes needs write access to the mHelpDesk job layer. The REST API's read-only coverage makes this workflow inaccessible through the official channel. Integuru makes bidirectional dispatch automation available from the first call.

Cleaning franchise and multi-location management platforms. list_jobs and get_job_detail feed the job-level data that franchise platforms need: completion rates across locations, revenue per crew, and schedule adherence metrics. Cleaning franchises running mHelpDesk across multiple franchise accounts need to aggregate this data programmatically. The REST API supports basic job reads, but multi-account aggregation at production polling frequency requires a throughput and reliability level that the documented API does not guarantee.

Workforce and technician management platforms. get_technicians and get_schedule give workforce tools a live view of the mHelpDesk technician roster and their current dispatch assignments. Platforms that synchronize mHelpDesk scheduling data with payroll systems, timesheet tools, or route-planning engines need this data on a regular cadence, applying the same HTTP-layer pattern Integuru uses across field service platforms with limited or no public APIs.

mHelpDesk Workflows This Integration Covers

The ten planned actions cover the core operational loop of a service business running on mHelpDesk:

• Job management: list_jobs and get_job_detail surface the active and historical job roster with customer contact, technician assignment, and invoice linkage. These anchor every downstream CRM, analytics, and dispatch workflow.
• Job lifecycle operations: create_job and update_job_status cover the full job cycle from creation through completion, giving AI schedulers and CRM tools write access to the mHelpDesk job layer the REST API does not expose.
• Customer management: list_customers and get_customer_detail handle the full customer record lifecycle for CRM sync and service history retrieval.
• Invoicing: list_invoices and get_invoice_detail provide structured invoice data with line items and payment status for accounting sync pipelines.
• Technician and dispatch management: get_technicians and get_schedule return the technician roster and dispatch schedule for workforce planning, AI routing tools, and payroll sync platforms.

Adjacent Integrations

Integuru already operates in the field services vertical with live production integrations across job scheduling, customer management, technician dispatch, and invoicing workflows. Teams building tools for cleaning franchises, HVAC contractors, and handyman services will find the same HTTP-layer approach applies directly to other platforms in this segment, including those where official APIs stop short of write operations entirely.