canonical: https://jentic.com/apis/aeroworkflow.com/aeroworkflow

# Aeroworkflow Aero API

Jentic publishes the only available OpenAPI specification for Aero API, keeping it validated and agent-ready. Aero Workflow is a practice-management platform built for accounting and bookkeeping firms, and Aero API exposes the underlying entities - Aeros (appointments, emails, tasks, others), MasterAeros (recurring work), Companies, Contacts, Projects, time entries, hats, and money entities - through a REST surface scoped per account. The 39 endpoints cover create-and-list operations on every Aero type, template-driven task creation, time tracking, and a SQL-style query endpoint for ad-hoc reads. Authentication uses an apikey header issued from the Aero Workflow account.

## For AI agents

Manage Aero Workflow practice-management work - appointments, emails, tasks, recurring jobs, companies, contacts, time entries - across 39 REST endpoints scoped per account.

## Scope

Does not handle bookkeeping ledgers, payroll, or invoicing - use for Aero Workflow practice management of tasks, time, clients, and recurring work only.

## Capabilities

- Create and list Aero appointments, emails, tasks, and other work items per account
- Spin up tasks from saved templates or library templates with a single POST
- Track time entries against any Aero work item with /AeroTimes endpoints
- Manage Companies, Contacts, Projects, Hats, Money Entities, and Team Members
- Drive recurring work through MasterAeros - create from template, add or pull steps, and insert occurrences
- Run SQL-style ad-hoc queries via /Sql/Select for custom reporting

## Use cases

### Accounting Firm Workflow Automation

Automate the creation of recurring monthly and quarterly work for an accounting practice. POST /api/{accountId}/v1/MasterAeros/FromTemplate/{id} spins up a recurring schedule from a saved template, /MasterAeros/{id}/InsertOccurrencesByDate adds occurrences for new periods, and /AeroTasks/FromTemplate/{id} creates one-off tasks against a client. Combined, these remove the manual click-through normally needed at month-end.

Example prompt: Call POST /api/{accountId}/v1/MasterAeros/FromTemplate/{id} with start_date=2026-07-01 to create the next quarter's recurring close work for a client

### Client and Project CRUD

Sync Aero Workflow with a CRM or onboarding tool by creating Companies and Contacts via API. POST /Companies and POST /Contacts create the records, GET /Companies/Query searches them, and GET /Companies/{id}/VaultEntries lets a vault entry be added when client credentials need to be stored alongside the company record.

Example prompt: Call POST /api/{accountId}/v1/Companies with the new client's name and details, then POST /api/{accountId}/v1/Contacts to add the primary contact

### Time Tracking and Reporting

Capture time spent on every Aero work item by writing time entries through /api/{accountId}/v1/Aero{category}s/{aeroId}/AeroTimes. Pair with /Sql/Select for custom reporting that pivots time by team member, hat, or client. Useful for firms that want lightweight integration with external invoicing or BI dashboards without using the Aero UI.

Example prompt: Call POST /api/{accountId}/v1/AeroTasks/{aeroId}/AeroTimes with hours=2.5, hatId, and a description to log time against an existing task

### AI Agent Practice Assistant

Let an AI agent manage a bookkeeping firm's daily work - list today's appointments, create follow-up tasks, log time, and search clients - through a single conversational interface. Through Jentic, the agent searches by intent for the right Aero operation, loads the schema, and executes with the apikey isolated in the vault.

Example prompt: Search Jentic for 'create an aero task from a template', load /AeroTasks/FromTemplate/{id} schema, and execute with the template ID and accountId

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/{accountId}/v1/AeroTasks | Create an Aero task |
| POST | /api/{accountId}/v1/AeroTasks/FromTemplate/{id} | Create a task from a saved template |
| POST | /api/{accountId}/v1/MasterAeros/FromTemplate/{id} | Create a recurring MasterAero from a template |
| GET | /api/{accountId}/v1/Companies | List companies in an account |
| POST | /api/{accountId}/v1/Companies | Create a new client company |
| POST | /api/{accountId}/v1/AeroTasks/{aeroId}/AeroTimes | Log a time entry against a task |
| POST | /api/{accountId}/Sql/Select | Run an ad-hoc SQL select query |

## Key resources

- **AeroAppointments** — List and create scheduled appointments
- **AeroEmails** — List and create email-tracked work items
- **AeroTasks** — List, create, and template-create task work items
- **AeroTimes** — Log time entries against Aero work items
- **MasterAeros** — Manage recurring work, steps, and occurrence schedules
- **Companies** — Manage client company records and search
- **Contacts** — Manage contacts associated with companies
- **Projects** — List projects in an account
- **Hats** — Retrieve role/hat assignments used for time tracking
- **TeamMembers** — List team members in an account
- **Sql** — Run ad-hoc SQL select queries for custom reporting

## Why Jentic

- **Setup:** Wiring the Aero API by hand means learning its apikey header and threading the accountId through a deep path structure for every task, company, and time operation. Through Jentic you install once, import the Aero API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Aero puts the accountId in the URL path (/api/{accountId}/v1/...), so a rule can pin the agent to one account. You choose which operations it may call, such as creating a task or reading companies, so broad SQL select operations are not included unless you add them.
- **Credential handling:** Your Aero apikey is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an Aero task from a template', and Jentic returns the matching operation with its accountId and template-id parameters so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **monday.com** — General-purpose work management platform with broad integrations
- **Pipedrive** — Sales CRM that pairs with practice-management to handle prospects
- **HubSpot Contacts API** — CRM contacts as the marketing-and-sales source for new Aero clients

## FAQ

### Why is there no official OpenAPI spec for the Aero API?

Aero Workflow does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Aero API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Aero API use?

Aero uses an apikey header on every request. The key is generated inside the Aero Workflow account settings and is scoped to a specific accountId, which is also a path parameter on every endpoint. Through Jentic the key is stored in the vault and injected at execution time.

### Can I create recurring work through the Aero API?

Yes. POST /api/{accountId}/v1/MasterAeros/FromTemplate/{id} or /MasterAeros/FromLibraryTemplate/{id} creates a recurring MasterAero from a saved template, and the /InsertOccurrences, /InsertOccurrencesByCount, and /InsertOccurrencesByDate endpoints add new occurrences to an existing schedule.

### How do I log time against an Aero task?

Call POST /api/{accountId}/v1/Aero{category}s/{aeroId}/AeroTimes with the hours, hatId, and description. The category placeholder takes the work-item type (Tasks, Appointments, Emails, Others) and aeroId references the specific work item.

### What are the rate limits for the Aero API?

Aero applies per-account throttling but does not declare specific limits in the spec; check the Aero Workflow knowledge base or contact support for your account's allowance. HTTP 429 responses are passed through Jentic so agents can back off.

### How do I create a templated task through Jentic?

Run pip install jentic, search Jentic with 'create an aero task from a template', load the /AeroTasks/FromTemplate/{id} schema, and execute with the template id, accountId, and any company or contact references. Jentic injects the apikey at execution time.

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

Yes. Because you run Jentic One yourself, your own rules decide which Aero operations and credentials the agent may use. Since the accountId lives in the URL path (/api/{accountId}/v1/...), you can pin the agent to a single Aero Workflow account, and you choose exactly which operations it may call, such as creating a task or listing companies. Broad reads like the /Sql/Select query endpoint stay out of reach unless you explicitly allow them.