JobNimbus API
JobNimbus is a cloud CRM and project management platform built for roofing, siding, gutters, fencing, and specialty contractors—covering leads, sales, estimates, scheduling, production, invoicing, and payments. An unofficial API lets you programmatically pull contacts, jobs, work orders, estimates, invoices, tasks, and activities—and push updates like new leads, job status changes, estimates, and invoices back into JobNimbus.
What is JobNimbus?
JobNimbus is a cloud-based CRM and business management platform purpose-built for contractor businesses in roofing, siding, gutters, fencing, and related trades. Contractors use JobNimbus to organize leads, build estimates and proposals, schedule jobs, manage production with photo and document workflows, collect payments, and track profit per job—across a web interface and 4.8-star iOS and Android mobile apps.
Core product areas include:
- Sales & CRM (lead organization, sales automation, estimates and proposals via SumoQuote)
- Operations (job scheduling, work orders, project management boards, custom workflows)
- Billing & Payments (invoicing, JobNimbus Payments for card/ACH, built-in financing via Wisetack)
- Communications (text messaging, email, Caller ID)
- Measurements (aerial roof measurement ordering via EagleView and HOVER)
- Analytics & Reporting (custom reports, profit tracking, performance insights)
Common data entities:
- Contacts, Leads, Companies
- Jobs, Work Orders, Workflow Statuses
- Estimates, Proposals, Material Orders
- Invoices, Payments, Financing Applications
- Tasks, Activities, Notes, Photos, Documents
The JobNimbus Integration Challenge
Contractors run their entire sales-to-cash workflow on JobNimbus, but turning that field- and mobile-driven activity into reliable API automation has real friction:
- REST-like, JSON-only Open API: the public API exposes GET, PUT, and POST against app.jobnimbus.com/api1, but coverage and object shapes vary across jobs, contacts, and related records
- Mobile-first data capture: much of the production data—photos, annotations, signatures, field notes—originates in the mobile apps and is awkward to extract at scale
- API-key access model: each integration relies on a per-user API key with that user's access rights, so permissions and actor context must be managed carefully
- Per-event webhooks: webhooks must be configured event-by-event and split by whether you primarily key off Jobs or Contacts, making full change capture fiddly
- Custom workflows and fields: contractors heavily customize statuses, boards, and custom fields, so generic integrations break across accounts
- Integration sprawl: QuickBooks, EagleView, CompanyCam, SumoQuote, Wisetack, supplier portals, and Zapier each move slices of data, leaving gaps a unified API has to close
How Supergood Creates JobNimbus APIs
Supergood combines JobNimbus's Open API with reverse-engineered authenticated flows to deliver a resilient, normalized API layer for your JobNimbus account—covering both web and mobile-originated data.
- Manages API keys and authenticated sessions securely, with correct actor context per request
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across contacts, jobs, estimates, invoices, and payments so you integrate once and rely on consistent objects
- Aligns with your custom workflow statuses, boards, and custom fields rather than forcing a generic schema
Use JobNimbus with AI agents: JobNimbus MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, custom workflows, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready JobNimbus adapter tailored to your account configuration and custom fields.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as JobNimbus evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a JobNimbus account using an API key and actor context, and obtain a session for downstream calls.
Contacts
/contactsList contacts and leads with filters for status, sales rep, source, and date range.
Contacts
/create_contactCreate a new contact or lead with name, address, source, and custom field values.
Jobs
/jobsRetrieve jobs and work orders with workflow status, assignment, and related-contact filters.
Jobs
/create_jobCreate a new job against a contact with type, workflow status, and custom fields, or update its status.
Billing
/invoicesPull estimates, invoices, and payment records with status, amount, and job filters.
Use Cases
Sync leads and contacts into your CRM and marketing stack
- Pull contacts, leads, and sources from JobNimbus into a single warehouse - Push new web and call-tracking leads into JobNimbus with the right workflow status - Reconcile sales-rep assignment and lead source across systems for unified reporting
Automate job and production tracking
- Stream job creation and workflow-status changes to downstream scheduling and ops tools - Sync work orders, tasks, and activities so field and office stay aligned - Surface stalled or aging jobs to retention and follow-up workflows
Reconcile estimates, invoices, and payments
- Sync estimates, invoices, and payments from JobNimbus into accounting and BI systems - Match JobNimbus Payments and financing applications against jobs for profit tracking - Flag unpaid invoices and overdue balances to collections workflows
Unify field data across mobile and integrations
- Pull photos, documents, and notes captured in the mobile apps into central storage - Consolidate EagleView, HOVER, CompanyCam, and SumoQuote artifacts against each job - Keep QuickBooks, supplier, and Zapier flows in sync through one normalized API
Technical Specifications
Authentication
Per-user API key plus actor context, handled in a managed session
Connectivity
JobNimbus Open API (app.jobnimbus.com/api1) augmented with authenticated browser flows where coverage is thin
Response format
Normalized JSON across Contacts, Jobs, Estimates, Invoices, and Payment objects
Rate limits
Adaptive throttling tuned to your account to avoid JobNimbus-side limits
Session management
Automatic key rotation, session refresh, and actor-context handling
Data freshness
Near real-time pulls for contacts, jobs, and invoices with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access keys, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for new and updated Jobs and Contacts, normalized across both event families
Latency
Sub-second reads on cached entities; multi-second writes when posting jobs, estimates, and invoices
Throughput
Horizontally scaled workers sized to high-volume contractor lead and job flows
Reliability
Retry, backoff, and idempotency keys for job, estimate, and invoice writes
Adaptation
Continuous monitoring of JobNimbus API and UI changes and per-account configuration drift
Frequently asked questions
Yes. Supergood builds on the JobNimbus Open API (REST-like, JSON, GET/PUT/POST against app.jobnimbus.com/api1) and supplements it with authenticated flows where the public API doesn't cover an entity, so you get complete, consistent access.
JobNimbus authenticates with a per-user API key carrying that user's access rights. Supergood manages the key securely, applies the correct actor context per request, and rotates credentials as needed.
Yes. JobNimbus webhooks fire per event and are split by Jobs versus Contacts. Supergood normalizes those callbacks into a single change stream and backs them with polling so no updates are missed.
Yes. Each account is profiled against its configured workflow statuses, boards, and custom fields. Supergood preserves your specific values rather than forcing a generic schema.
Yes. Photos, notes, documents, and field activity captured in the JobNimbus iOS and Android apps are exposed through the same normalized API surface alongside web-created records.