Ascora API
Ascora is field service management software built for trade businesses—electricians, plumbers, HVAC, construction, and more—covering leads, quoting, scheduling, job management, inventory, timesheets, and invoicing. An unofficial API lets you programmatically pull jobs, quotes, customers, schedules, timesheets, and invoices—and push updates like new jobs, quotes, bookings, and payments back into Ascora.
What is Ascora?
Ascora is field service management software built specifically for trade businesses since 2009. It targets contractors who have outgrown basic tools and need to manage complex, multi-crew operations—covering leads, quoting and estimating, scheduling and dispatch, job tracking, inventory, timesheets, compliance forms, and invoicing with payments, all with offline field functionality on mobile.
Core product areas include:
- Leads Management (capture and track leads from calls, forms, or social media)
- Quoting & Estimating (multi-stage quotes with win-rate tracking)
- Scheduling & Booking (drag-and-drop dispatch for multiple crews)
- Field Service Management (job tracking with status, costs, and tasks)
- Inventory Management (stock monitoring across vans and sites)
- Timesheets (GPS-logged hours synced to jobs and payroll)
- Invoicing & Payment (instant invoice generation and payment processing)
- Compliance Forms and Project Staging (digital SWMS, JSAs, checklists, progress claims, and retentions)
Common data entities:
- Leads, Quotes, Estimates, Win Rates
- Jobs, Tasks, Job Costs, Statuses
- Schedules, Bookings, Crews, Technicians
- Customers, Sites, Service Plans
- Inventory Items, Stock Levels, Suppliers
- Timesheets, Invoices, Payments, Progress Claims
- Compliance Forms, Checklists, Photos, Attachments
The Ascora Integration Challenge
Trade businesses run mission-critical operations on Ascora daily, but turning a mobile-first, portal-driven field service platform into reliable API-driven automation is non-trivial:
- Single active API key: Ascora supports one active API key per account—rotating or regenerating it forces a full reauthorization, which complicates multi-system integrations
- Mobile-first field data: Jobs, timesheets, GPS hours, photos, and compliance forms are captured offline in the field app and sync later—values can lag or change after upload
- Accounting and supplier gateways: Much data flows through Xero, MYOB, QuickBooks, Reece maX, and EzzyBills connectors, each with its own sync rules and field mappings
- Multi-crew scheduling state: Drag-and-drop dispatch, bookings, and crew assignments change constantly, so schedule reads need careful change detection
- Quote-to-invoice lifecycle: Multi-stage quotes, job costs, progress claims, retentions, and invoices each have their own states and effective dates
- Endpoint coverage variability: The open API and Zapier connector cover common entities, but some compliance, project staging, and reporting data is only reachable through the UI
How Supergood Creates Ascora APIs
Supergood reverse-engineers authenticated browser and mobile flows alongside Ascora's open API to deliver a resilient, normalized API layer for your Ascora account—covering jobs, scheduling, quoting, timesheets, and invoicing in one place.
- Manages API token generation and reauthorization so single-key rotation never breaks your integration
- Maintains session continuity with automated refresh and change detection across mobile and web surfaces
- Normalizes responses across Leads, Quotes, Jobs, Scheduling, Timesheets, and Invoicing so you integrate once and rely on consistent objects
- Reconciles field-synced data—offline timesheets, photos, and compliance forms—as it lands from the mobile app
Use Ascora with AI agents: Ascora MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, crews, accounting connectors, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Ascora adapter tailored to your account configuration and field workflows.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Ascora evolves.
API Endpoints
Authentication
/authenticateAuthenticate to an Ascora account using your generated API key and obtain a session token for downstream calls.
Jobs
/jobsList jobs with filters for status, crew, customer, scheduled date, and job costs.
Jobs
/create_jobCreate a new job from a lead or quote, assign a crew, and set tasks, site, and scheduled time.
Quoting
/quotesRetrieve multi-stage quotes and estimates with win-rate, status, and customer filters.
Scheduling
/schedulesPull crew schedules and bookings across multiple crews with date-range and technician filters.
Billing
/invoicesRetrieve invoices, payments, and progress claims with status, customer, and date filters.
Use Cases
Sync jobs and scheduling into your operations stack
- Pull active jobs, tasks, and statuses with crew and customer context into a single warehouse - Stream schedule and booking changes to downstream dispatch, BI, and customer-notification tools - Reconcile customer and site records across Ascora and your CRM for a unified view
Automate quote-to-job and invoicing workflows
- Push new quotes and estimates and pull win-rate data back for sales reporting - Convert accepted quotes into jobs with crews, tasks, and scheduled times without portal clicks - Generate invoices, progress claims, and payments and sync them to your accounting system
Reconcile timesheets and payroll
- Pull GPS-logged timesheets synced from the field app for payroll export - Match labor hours and job costs against jobs for accurate margin reporting - Surface incomplete or unsynced timesheets to back-office review queues
Centralize inventory and compliance data
- Sync stock levels across vans and sites into inventory and purchasing systems - Pull completed compliance forms, SWMS, JSAs, checklists, and photos for audit archives - Trigger reorder and supplier workflows when stock falls below thresholds
Technical Specifications
Authentication
Ascora API key (single active key per account) managed in a secure session with automatic reauthorization
Connectivity
Authenticated web and mobile flows plus Ascora's open API and Zapier connector where exposed
Response format
Normalized JSON across Jobs, Quotes, Scheduling, Timesheets, Inventory, and Invoicing objects
Rate limits
Adaptive throttling tuned to your account to avoid Ascora-side limits
Session management
Automatic session refresh, API key rotation handling, and credential management
Data freshness
Near real-time pulls for jobs, schedules, and invoices with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for job status, schedule changes, quote acceptance, and invoice events
Latency
Sub-second reads on cached entities; multi-second writes when posting jobs, quotes, and invoices
Throughput
Horizontally scaled workers sized to multi-crew job and timesheet volume
Reliability
Retry, backoff, and idempotency keys for job, invoice, and payment transactions
Adaptation
Continuous monitoring of Ascora releases, accounting connector changes, and account-specific configuration drift
Frequently asked questions
Yes. Ascora allows one active API key per account, and regenerating it forces reauthorization. Supergood manages key generation and reauthorization so rotation never silently breaks your integration.
Yes. Jobs, GPS timesheets, photos, and compliance forms captured offline sync to Ascora and are exposed through the same normalized API surface once they land, with change detection for late-arriving updates.
Ascora already syncs invoices and payments to Xero, MYOB, and QuickBooks. Supergood reads the same billing entities and can push updates, so your accounting system and downstream tools stay reconciled.
Leads, quoting and estimating, scheduling and dispatch, job management, inventory, timesheets, compliance forms, project staging, and invoicing are all exposed through one normalized API.
Yes. Crew schedules, bookings, and technician assignments are read with change detection so multi-crew dispatch state stays in sync with your downstream systems.