JobNimbus API Guide for Roofers and Exterior Contractors

One-line verdict: The API is unlimited on every plan — the catch is a single admin-issued key whose access profile decides what your automations can actually see. Openness: 4 / 5 — rated 4 because JobNimbus documents a public API with webhooks available on all plans, held back from 5 by the admin-key setup gate and money endpoints that don’t appear in the vendor’s API document.

The connection that works

Rung 1 — Direct connection. JobNimbus documents a REST-style API that exchanges JSON, and its pricing page lists “API & Webhooks: Unlimited” on every plan — Essentials through Enterprise. There is no plan gate and no partner application. Access runs through an API key your admin creates in Settings → API. The key is an admin-level token, and what it can see and do is set by the Access Profile attached to it. There is no OAuth sign-in flow in the vendor’s API documentation — the key is the credential, so it gets stored and guarded like a password.

What’s verified in the vendor’s API document: contacts — read with flexible filtering, and creation is demonstrated in the document’s own examples. Contacts, jobs, and notes are named as the commonly used endpoints, with the shared query pattern documented. What is not in that document matters just as much: no estimates, invoices, or payments endpoints appear in it (see Can’t automate).

Webhooks, JobNimbus-style: instead of a subscribe-by-topic catalog, webhooks are an action inside Automation rules — when a rule fires (the vendor’s guides use events like a Contact or Job being created), JobNimbus sends the record’s fields to your address. Documented payload types: Contacts, Jobs, Tasks, Work Orders, Material Orders, and Activity. One sharp limit, in the vendor’s own help: custom fields are not included in webhook payloads. And mind the plan table: lower tiers cap your count of active automations (10 on Essentials), which caps how many of these webhook rules you can run.

Bridge apps: JobNimbus’s own help center documents its Zapier app — triggers for Contact and Job created, modified, and deleted; actions to Create Job, Create Contact, Update Contact, and Create Attachment. No native Make app was found.

Can automate

• Speed-to-Lead — a new contact created in JobNimbus can fire an automation webhook immediately, so follow-up starts in minutes; new contacts can also be pushed in from your lead sources through the API or Zapier.
• Job pipeline signals — job created/modified events (via Automation webhooks or Zapier) can drive status texts, review asks, and crew notifications.
• Contact sync — contacts are readable with rich filtering, so your CRM, dialer, or marketing tool can work from the same list.
• Attachments in — Zapier can create attachments on records, handy for photos and documents arriving from other tools.

Can’t automate

• Estimates through the API — UNVERIFIED. Estimates are a product feature (the SumoQuote experience is built in), but no estimates endpoint appears in the vendor’s API document. Estimate follow-up keyed off the estimate itself is UNVERIFIED.
• Invoices and payments through the API — UNVERIFIED. Both are plan features; neither appears as an endpoint in the API document. No invoice-chase build should rest on this API today.
• Job write operations, endpoint by endpoint — UNVERIFIED. Jobs are a named endpoint with a documented read pattern, but the API document’s worked write examples cover contacts; job creation is verified only on the Zapier bridge, which is bridge evidence, not API proof.
• Custom fields over webhooks — verified limitation: webhook payloads exclude custom fields, so a workflow keyed on a custom field needs an API lookup after the alert, not the alert alone.
• Published rate limits — UNVERIFIED. JobNimbus publishes no API rate limit in the documents we read; plan for sensible pacing anyway.

Hidden gate: Your admin has to create the API key and pick its access profile — pick too narrow a profile and the connection quietly can’t see or do what you paid for. Test the key against every object the automation touches before you call the build done.

Build fit — what this platform supports well

• Speed-to-Lead — strong fit: contact events fire immediately through Automation webhooks, on every plan.
• Estimate Follow-Up — partial: follow-up can key off job stage changes, but the estimate object itself is UNVERIFIED in the API.
• Missed-Call / After-Hours Capture — works: a captured call becomes a contact (API or Zapier) and the follow-up fires from there.
• Invoice Chase / AR — not on this API: invoices and payments are UNVERIFIED; the chase runs on our messaging layer.
• Review Engine — like every platform here, JobNimbus has no verified reviews API (its review story is partner tools like BirdEye/Podium, not an API), so the review ask runs on our system triggered by a job-completion signal.

What this means for your shop

If you run JobNimbus, you’re better positioned than most roofers: the API and webhooks are on your plan already, whatever plan that is. The discipline is in the setup — one admin key, scoped by one access profile. Get the profile right, verify each object the automation touches, and the front of your pipeline can move on its own. Just don’t let anyone sell you invoice automation on this API until the vendor documents the endpoint.