canonical: https://jentic.com/apis/au.app.clio.com/au-app-clio

# Au App Clio Clio API Documentation (Australia)

This page describes a curated, agent-optimized Jentic OpenAPI specification for the Clio API in the Australian region, kept validated and agent-ready. Clio also publishes its own OpenAPI document on its developer-documentation site, covering all four production regions in one file; the Jentic variant is pinned to the Australian base URL, and the FAQ below links Clio's document so you can compare the two. The Clio API (Australia region) gives Australian law firms programmatic access to Clio Manage, the cloud practice-management platform used by tens of thousands of legal teams. The v4 surface covers 282 endpoints across matters, contacts, activities, calendars, bills, trust accounting, documents, and tasks, with regional data residency at au.app.clio.com. Authentication is OAuth 2.0, and the API is the same shape as the US, EU, and CA regions so integrations port across regions by base URL alone.

## For AI agents

Read and write matters, contacts, activities, bills, calendar entries, and documents in an Australian-region Clio Manage account using OAuth 2.0.

## Scope

Does not handle court e-filing, conveyancing search portals, or document automation templates - use for Clio Manage practice-management data in the Australian region only.

## Capabilities

- Create a new matter and attach billable clients via /matters.json and /billable_matters.json
- Log a billable activity against a matter using POST /activities.json
- Pull every contact in the firm with paginated GET /contacts.json
- Generate a draft bill for a matter through /bills.json and bill_themes
- Schedule a calendar entry tied to a matter via /calendar_entries.json
- Move funds between trust and operating accounts using /bank_transfers.json
- Upload and version case documents through the Clio Files endpoints

## Use cases

### Time capture and billing automation for AU firms

Australian law firms lose revenue when fee earners forget to log time. An agent integrated with the Clio Australia API can ingest calendar entries and email metadata, post a matching activity through POST /activities.json with the correct activity_description and rate, and roll the activities into a draft bill via /bills.json once a billing period closes. This collapses end-of-month reconciliation from days to minutes and keeps the trust ledger clean.

Example prompt: Read the firm's calendar entries from yesterday via GET /calendar_entries.json, and for each entry tagged with a matter ID, POST a new /activities.json entry with the duration, activity_description_id, and matter_id.

### Client and matter intake portal

When a new enquiry arrives through a website form, an intake agent can create a contact via POST /contacts.json, create a matter via POST /matters.json that links to the contact, and write the initial conflict-check note as a custom_field. /allocations.json then attaches the responsible solicitor. The Australian region base URL keeps client data resident in au.app.clio.com, satisfying APP and Privacy Act expectations.

Example prompt: Given an intake JSON object, create the Clio contact via POST /contacts.json, then create a matter via POST /matters.json with the new contact_id and a description of the engagement.

### Trust account reconciliation

Australian solicitors must reconcile trust ledgers regularly under state regulator rules. /bank_accounts.json, /bank_transactions.json, and /bank_transfers.json expose the operating and trust ledgers and the transfers between them. An agent can pull the prior day's transactions, match each entry to a matter, and flag any unmatched movements for the bookkeeper before close of business.

Example prompt: Pull GET /bank_transactions.json filtered to the last 24 hours, match each transaction to an existing /matters.json record by reference, and post a list of unmatched transactions to a Slack channel.

### AI agent integration via Jentic

A practice-assistant agent built on Jentic can call the Clio Australia API without storing OAuth tokens in prompt memory. The agent searches an intent like 'create a new matter in Clio', Jentic returns the matching operation and its input schema, and execution uses the OAuth token resolved from your Jentic One instance. Token refresh and the regional au.app.clio.com base URL are handled automatically.

Example prompt: Use Jentic search 'create a new Clio matter', load the schema for POST /matters.json, and execute it with description='Estate planning - Smith' and client_id from a prior /contacts.json call.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/matters.json` | List all matters in the firm |
| POST | `/matters.json` | Create a new matter |
| POST | `/activities.json` | Log a billable activity against a matter |
| GET | `/contacts.json` | List contacts and clients |
| POST | `/contacts.json` | Create a new contact |
| POST | `/bills.json` | Create a draft bill for a matter |
| GET | `/bank_transactions.json` | List trust and operating account transactions |
| POST | `/calendar_entries.json` | Create a calendar entry tied to a matter |

## Key resources

- **Matters** — Create, list, update, and delete legal matters with billing client and responsible-solicitor relationships
- **Contacts** — Manage clients and other persons across the firm with custom fields and relationships
- **Activities** — Log billable and non-billable time and expenses against matters
- **Bills** — Generate, edit, send, and reconcile invoices using bill themes
- **Bank Accounts** — Operating and trust account ledgers, transactions, and transfers
- **Calendars** — Schedule appointments, court dates, and reminders tied to matters

## Why Jentic

- **Setup:** Wiring the Clio API in the Australian region by hand means running its OAuth 2.0 flow, rotating refresh tokens, and picking a path from hundreds of practice-management endpoints on the au host. Through Jentic you install once, import the Clio API Documentation (Australia) from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Clio reaches matters, contacts, and bills through collection endpoints and request bodies rather than a resource id in the URL path here, so limit the agent to the operations it needs, such as listing or creating matters. You choose the operations it may call, so posting bills is not included unless you add it.
- **Credential handling:** Your Clio OAuth tokens are stored once, encrypted, by your own Jentic One instance, which rotates the refresh token and injects the access token at execution time. The raw token never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a new matter in Clio', and Jentic returns the matching Clio operation with its input schema so the agent picks the right endpoint without scrolling the full reference.

## Related APIs

- **Clio API (US)** — Same v4 API surface but hosted in the US data region for US firms.
- **Stripe API** — Stripe powers payment links and card-on-file charges that pair with Clio invoices.
- **HubSpot CRM API** — HubSpot manages marketing and intake before a contact becomes a Clio client.

## FAQ

### Which OpenAPI specification does this Clio API Documentation (Australia) page describe?

A curated, agent-optimized Jentic specification covering 282 Clio operations against the Australian base URL https://au.app.clio.com/api/v4. Clio also publishes its own OpenAPI document at https://docs.developers.clio.com/openapi.json, which is one region-generic file listing all four production servers (US, EU, Canada, and Australia) across 166 paths and 301 operations. The Jentic variant is pinned to the Australian region and is validated against the live API and kept up to date, so it is a curated Jentic spec rather than a silent substitute for Clio's document. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Clio Australia API use?

The Clio Australia API uses OAuth 2.0 authorization-code flow against au.app.clio.com. Apps register in the Australian developer portal, exchange an authorization code for an access and refresh token, and pass the access token as a Bearer header. Through Jentic the OAuth tokens are stored in the vault and refreshed automatically.

### Can I create matters and log time with the Clio Australia API?

Yes. POST /matters.json creates a matter with a description, client_id, and responsible solicitor, and POST /activities.json logs billable or non-billable time against a matter_id with a duration and activity_description_id. The same endpoints support PATCH for edits and DELETE for removal.

### What are the rate limits for the Clio Australia API?

Clio enforces a rolling per-application rate limit and a per-token concurrency limit. Limits are not declared in the spec; the documented production figure on the Clio developer portal is 100 requests per 15 seconds per application, with bursts above that returning 429. Use the X-RateLimit response headers to back off.

### How do I generate a bill for a matter through Jentic?

Run jentic search 'create a Clio bill for a matter', load the schema for POST /bills.json, and execute it with the matter_id and a bill_theme_id. The OAuth token is resolved from your Jentic One instance at execution time. With pip install jentic an agent can produce the draft invoice in one async call.

### Does the Australian region keep data in Australia?

Yes. au.app.clio.com is the Australian data region, separate from the US (app.clio.com), Canadian (ca.app.clio.com), and EU (eu.app.clio.com) regions. Calls made against this base URL keep matter, client, and document data resident in Australia.

### Can I limit what my agent is allowed to do with the Clio Australia API?

Yes. Because you self-host Jentic One, your own rules decide which Clio operations and credentials the agent can use, and you grant only the endpoints it needs. Clio reaches matters, contacts, and bills through collection endpoints and request bodies rather than a resource id in the URL path, so you can allow read-only calls like GET /matters.json or GET /contacts.json while withholding write operations. Since you choose the operations, posting a draft bill through POST /bills.json or moving trust funds via /bank_transfers.json is not available to the agent unless you explicitly add it.