Aero API

Name: Aero API API
Brand: Aero API
Availability: InStock

★ Only Publicly Available SpecProductivityTask ManagementapiKey39 EndpointsREST

For Agents

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

Quickstart

Get started with Aero API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an aero task from a template"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Aero API API.

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

GET STARTED

Start building with Aero API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Aero API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Aero API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

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

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

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

Why though Jentic?

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

Credential isolation

Your Aero apikey is stored encrypted in the Jentic vault and injected as the apikey header at call time. Agents receive scoped execution rights and the raw key never appears in their context.

Intent-based discovery

Agents search by intent (e.g. 'create an aero task from a template') and Jentic returns the matching Aero operation with its accountId and template-id parameters, so the agent doesn't need to navigate the deep path structure manually.

Time to first call

Direct Aero integration: 1-2 days to wire auth, accountId routing, and the per-Aero-category endpoint patterns. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

monday.com

General-purpose work management platform with broad integrations

Choose monday.com for cross-functional work management; choose Aero when the team is an accounting practice using Aero-native concepts like Hats and MasterAeros

Complementary

Pipedrive

Sales CRM that pairs with practice-management to handle prospects

Use Pipedrive for the pre-sale pipeline and Aero for the post-sale practice-delivery work

Complementary

HubSpot Contacts API

CRM contacts as the marketing-and-sales source for new Aero clients

Use HubSpot Contacts to sync prospects into Aero Companies and Contacts when a deal closes

FAQs

Specific to using Aero API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.