Yes. Jobber has a GraphQL API with OAuth 2.0, and it supports private custom integrations for your own account without listing an app in the Jobber App Marketplace. An AI receptionist can create clients and requests from calls and give existing clients answers about their visits.
What the AI receptionist does in Jobber
Jobber's request is the natural place for a new call to land, because your team already reviews requests before quoting or scheduling.
- Creates a new client and property from the caller's details
- Creates a service request with the work described in plain language
- Looks up existing clients by phone number
- Answers questions about upcoming visits where your setup allows
- Texts a confirmation and asks for photos when they help
How the connection works
Jobber uses the OAuth 2.0 authorization code flow. A developer creates an app in Jobber's Developer Center, chooses the scopes it needs, and you approve it on the Jobber connection screen. Access tokens expire after 60 minutes and are refreshed automatically.
- You approve the connection from your own Jobber account
- Scopes limit what the receptionist can read and write
- Requests go to a single GraphQL endpoint over HTTPS
- You can disconnect the app at any time
Private integration, no marketplace needed
Jobber calls these custom integrations. An app built only for your business can stay in draft without an app review, as long as it connects to no more than five paying Jobber accounts.
- Built for your account and your call flow
- No public marketplace listing required
- Fits single businesses and small groups of locations
- Larger multi-account setups need Jobber's app review
A typical call
A homeowner calls a landscaping company in March asking about spring cleanup and weekly mowing. The receptionist asks about the property size and timing and checks the service area.
- New client and property created in Jobber
- Request created for spring cleanup and recurring mowing
- Assessment offered if you use them
- Your team quotes from the request the next morning
Limits to plan for
The API reflects how Jobber works, so the integration should too.
- Pricing usually stays with your team, through quotes
- Booking visits directly needs clear rules about crews and capacity
- Spring and storm-season spikes need enough request-review time
- API versions change, so the integration is pinned to a version and updated
Setup steps
A Jobber integration is usually live in two to four weeks.
- Define what makes a good request: details, photos, property notes
- Create the custom integration and approve it on your account
- Test client and request creation with real call scenarios
- Launch on after-hours and missed calls, then expand
Frequently asked questions
Does Jobber have an API?
Yes. Jobber offers a GraphQL API with OAuth 2.0 through its Developer Center.
Do we need a Jobber marketplace app?
No. A custom integration for your own account can stay in draft without an app review if it connects to five or fewer paying Jobber accounts.
Can the AI receptionist create quotes?
We recommend it creates requests and leaves pricing to your team, since most service quotes depend on a site visit or photos.
Will it work for lawn care, cleaning, and HVAC?
Yes. The call flow changes by trade, but the Jobber side, clients and requests, works the same way.
What does it cost?
Integrated AI receptionist builds typically cost $5,000 to $15,000, plus monthly usage. Simpler setups that send summaries instead of writing to Jobber cost less.
Sources
- Limitations for Custom Integrations (Jobber Developer Center)
- App Authorization (OAuth 2.0) (Jobber Developer Center)