RealGreen API Guide for Lawn and Landscape Contractors

One-line verdict: The API is real enough to sell as a plan feature — and undocumented enough that nobody outside WorkWave can tell you what it actually does. Openness: 2 / 5 — rated 2 because RealGreen states API access on its higher plans but publishes no developer documentation at all: no endpoints, no auth model, no rate limits, nothing a builder can verify.

The connection that works

Start with what the vendor itself states. RealGreen’s Service Assistant 5 (SA5) — “RealGreen by WorkWave” — is the CRM at the center of its lawn-care system. Its own plan grid lists “API Integration” on the Professional package and “Advanced API Integration” on Enterprise; the Small Business package lists neither. Pricing is quote-based. That plan line is the entire public documentation of this API: on every vendor source we searched, there is no endpoint reference, no authentication guide, no webhook documentation, and no rate limit. An API you can buy but cannot read about is a vendor-controlled door, and this page scores it as one.

Two concrete flows are verified from vendor pages. First, an inbound web-form webhook: RealGreen’s FAQ states you can connect external web forms to RealGreen via webhook — when a prospect submits the form, RealGreen creates a profile and sends a call-log notification. That is a real, narrow, lead-in door. Second, a case-study data pull: RealGreen’s own case study describes a customer who “added the API integration to Service Assistant 5, then used the API to create a dashboard that automatically updates every hour with the sales data,” and names lead-capture applications among API bundle uses. That’s a marketing case study — evidence the API moves sales data out and leads in, not an endpoint list.

Everything else about this API — its type, how a key is obtained, which objects can be read or written — appears only in third-party integrator material, which this directory does not count. Those claims sit in the UNVERIFIED list below, where they belong.

Bridge apps: no native RealGreen or Service Assistant app was found on Zapier. A Make app exists but is community-developed by a third party, explicitly “not maintained or supported” by Make, with limited documentation — weak bridge evidence only.

Can automate

• Web leads straight in — the vendor-documented form webhook turns a website submission into a RealGreen profile plus a call-log notification, no re-typing.
• Sales-data dashboards — per the vendor’s own case study, sales data can be pulled out on an hourly rhythm for reporting.
• Whatever WorkWave scopes with you — the API exists as a purchased feature; its real shape gets defined in the vendor conversation, not in public docs.

Can’t automate

• Any specific object through the API — UNVERIFIED. Customers, jobs/work orders, invoices, and payments are SA5 product features; no vendor source states any of them are readable or writable through the API.
• A self-serve connection — no documented key process, auth model, or developer sign-up exists in vendor materials. (A purchased-key/application process circulates in third-party integrator writing; it is not vendor-confirmed.)
• Outbound webhooks — none are documented; the only webhook in vendor sources points inward, from your form.
• Rate limits — none documented anywhere in vendor sources.
• A Zapier connection — no native app was found.

Hidden gate: You don’t get the API in the box — it’s a paid add-on on the higher plans, and WorkWave has to set it up with you. Get the scope of “API Integration” in writing before you count it as a connection.

Build fit — what this platform supports well

• Speed-to-Lead — the front door works: form leads land as profiles through the documented webhook. Follow-up itself runs on our messaging layer.
• Reporting — the case-study pattern (sales data out, hourly) is the one proven shape.
• Estimate Follow-Up / Invoice Chase — UNVERIFIED: no estimate or invoice API surface is documented; the chase keys off your accounting records.
• Review Engine — like every platform here, RealGreen has no verified reviews API (its “Online Reviews” is a product feature, not an API), so the review ask runs on our system.

What this means for your shop

If you run SA5 for lawn or landscape routes, treat “API Integration” as a conversation, not a feature: before renewal or upgrade, make WorkWave name — in writing — which data the API exposes, how a builder authenticates, and what the setup includes. Until that email exists, plan your automation around the two proven paths: leads in through the form webhook, sales numbers out for your dashboard.