Your business doesn’t run on one piece of software. Jobs, quotes and stock live in WorkGuru, but you might also have a CRM, a BI dashboard, a customer portal, a production system, or an AI assistant that could do a lot more with the right data.
Today we’re launching the WorkGuru Public API (v2): a documented, versioned REST API that lets your developer, IT partner or software tools read and update the data you already manage in WorkGuru.
It’s live now in Australia and New Zealand, with the UK following tomorrow.
What you can connect
The API covers 33 resource areas across the whole job lifecycle, from lead to quote, to project or stock sale, to invoice, plus the timesheets and purchase orders that feed project costs along the way.
- Sales: leads and quotes, including accepting and declining quotes
- Clients and suppliers: companies and their contacts
- Projects and production: projects, tasks and production jobs
- Time: timesheets, including bulk creation and approval
- Purchasing: purchase orders and supplier credit notes
- Stock: products, live stock levels, adjustments, stock sales and usage
- Billing: invoices, payments and client credit notes
- Assets and custom fields: assets with service history, and your own custom fields
Actions such as approving a timesheet or accepting a quote run the same business rules as they do in the app, so data that comes in through the API behaves just like data entered by your team.
What you could build
- Push accepted quotes from your CRM straight into WorkGuru projects
- Sync stock levels to your online store or customer portal
- Feed timesheets in from a field or production system
- Pull job and invoice data into your own dashboards
- Give an AI or automation tool structured, permission-controlled access to your operations
You stay in control
Getting started takes three steps:
- Create a key. An admin creates an API key in WorkGuru under Settings → API Keys.
- Set its scopes. Choose read and/or write access per area, such as “read quotes” or “write timesheets”. A key can only touch what it’s been granted.
- Connect. The integration exchanges the key and secret for a token using OAuth2, the industry-standard method, and starts calling the API.
Every key needs both the scope and the matching WorkGuru user permission, so scopes can narrow what a key does but never grant more than its permissions allow. Sensitive figures like project costs and margins are only returned to keys whose user can see them in the app. And a key only ever sees its own WorkGuru account.
Built for developers
- Interactive documentation where you can try any endpoint from the browser
- Consistent list, get, create, update and delete patterns across every area
- Pagination, sorting, filters and
modifiedSince, so you can sync only what’s changed - Readable, stable ids (for example
cl_…for a client) - Standard error responses (RFC 7807), each with a reference to quote to our support team
- Versioned at
/api/v2, so what you build today keeps working as WorkGuru evolves
Already using the WorkGuru API?
Nothing changes. Your existing integration and its keys keep working as they are.
To use v2, create a new API key with scopes. Leave the key your current integration uses as it is: adding scopes to it moves it onto the new API, and it will stop working with the old one.
Reporting endpoints aren’t in v2 yet, so if you rely on them, stay on v1 for now.
Get started
Explore the docs and try your first call.
Building an integration or partner product? We’d love to hear what you’re working on. Get in touch with our team.