Acrual API

Name: Acrual API
Brand: Acrual API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingbearer35 EndpointsREST

Install Jentic One Beta

Connect the Acrual API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Acrual API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Acrual API.

Retrieve client and supplier records to populate quotes and purchase orders

Create and read jobs, including invoiced status, attached files, and folders

Upload files and create folders inside a job for project documentation

GET STARTED

Start building with Acrual API

Explore with Jentic

View OpenAPI Document

For Agents

Manage clients, jobs, quotes, invoices, time entries, and supplier purchase orders in Acrual so agents can automate quoting, time logging, and invoicing for service businesses.

Use for: I want to create a new job for a client, Upload a contract PDF to an existing Acrual job, List all jobs that have not yet been invoiced, Retrieve a client's record before generating a quote

Not supported: Does not handle bookkeeping ledgers, GST/VAT filing, or card payment capture — use for job management, quoting, invoicing, and time tracking on Acrual only.

Jentic publishes the only available OpenAPI specification for Acrual API, keeping it validated and agent-ready. Acrual is a job management and invoicing platform for service businesses, and its API exposes 35 endpoints across clients, employees, jobs, quotes, invoices, purchase orders, suppliers, time entries, variations, hooks, integrations, and settings. Jobs can have files uploaded, folders created, and invoiced status retrieved. Authentication is bearer token, base URL is acrual.com/api/v1.0.

Use Cases

Patterns agents use Acrual API for, with concrete tasks.

★ Quote-to-Job Conversion Workflow

When a quote is accepted, an automation calls the quote endpoints to mark it won and the jobs endpoints to create the corresponding job record. The new job inherits client and pricing context from the quote. Service business owners stop double-entering data between sales and delivery and the same record carries through to invoicing.

On quote acceptance, create a new job tied to the same client and pre-fill its scope from the quote line items

Job File and Folder Management

A field team uploads site photos and signed documents straight into the job record by calling /jobs/{id}/files/upload and creating folders via /jobs/{id}/files/folder. Office staff find the right file inside Acrual instead of digging through email or shared drives. The job becomes the single source of truth for that engagement.

Create a 'Site Photos' folder under a given job and upload three images into that folder

Time Tracking Roll-Up to Invoices

Workers log time via a mobile app that posts entries to the time entries endpoint. End-of-week, an automation reads time entries by job, generates invoice line items, and creates the invoice via the invoices endpoints. Invoices ship within a day of work completion rather than at month-end.

Roll up time entries for last week per job, create one invoice per job, and email a summary to the operations manager

Agent-Driven Job Updates via Jentic

An AI assistant in a service business's chat tool answers 'what's the status of job 245?' or 'create a variation on job 245 for an extra day's work'. The agent calls Acrual through Jentic, looks up the job, and posts the variation. The bearer token never enters the agent's context.

Through Jentic, search 'create a variation on a job', load the variations endpoint, and create a variation for an extra day's labor on job 245

Key Endpoints

35 endpoints — jentic publishes the only available openapi specification for acrual api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/clients

List clients

GET

/clients/{id}

Retrieve a client record

GET

/jobs

List jobs

GET

/jobs/{id}

Retrieve a job

GET

/jobs/{id}/invoiced

Get invoiced status for a job

POST

/jobs/{id}/files/upload

Upload a file to a job

POST

/jobs/{id}/files/folder

Create a folder inside a job

GET

/employees

List employees

GET

/clients

List clients

GET

/clients/{id}

Retrieve a client record

GET

/jobs

List jobs

GET

/jobs/{id}

Retrieve a job

GET

/jobs/{id}/invoiced

Get invoiced status for a job

POST

/jobs/{id}/files/upload

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Acrual bearer tokens are stored encrypted in the Jentic vault. Jentic injects the Authorization header at execution time, so raw token values never appear in agent context or logs.

Intent-based discovery

Agents search by intent — for example, 'create a new job for a client' — and Jentic returns the matching jobs endpoint with its input schema and required client id parameter.

Time to first call

Direct integration: 2-3 days for bearer auth, file upload handling, and webhook setup. Through Jentic: under 1 hour for the first working job call.

FAQs

Specific to using Acrual API through Jentic.

Why is there no official OpenAPI spec for Acrual API?

Acrual does not publish a public OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Acrual API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Acrual API use?

Bearer token authentication on every request via the Authorization: Bearer <token> header. Through Jentic, the token is stored encrypted in the vault and injected at execution time, so the raw value stays out of agent context.

Can I upload files to a job through the Acrual API?

Yes. POST /jobs/{id}/files/upload uploads a file to the job and POST /jobs/{id}/files/folder creates a named folder. DELETE /jobs/{id}/files removes attachments. Use these to keep contracts, site photos, and inspection documents on the job record itself.

What are the rate limits for the Acrual API?

The OpenAPI spec does not document explicit rate limits. Treat the API as throughput-bounded by your Acrual plan and back off on HTTP 429. For batch sync of jobs and time entries, page through /jobs and /clients rather than fetching detail per record.

How do I create a job through Jentic?

Run pip install jentic, then search 'create a new job for a client'. Jentic returns the jobs endpoint with its input schema, you supply the client id and job description, and execute. The bearer token is injected at execution time.

Does the Acrual API expose webhooks?

Yes — the spec includes a hooks tag covering webhook subscription endpoints, which let you receive events when jobs, invoices, or other resources change. This avoids polling for status changes during long-running engagements.

Acrual API

Connect the Acrual API to your agent

Capabilities

Start building with Acrual API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs