canonical: https://jentic.com/apis/agiled.app/agiled

# Agiled App Agiled API

Jentic publishes the only available OpenAPI specification for Agiled API, keeping it validated and agent-ready. Agiled is an all-in-one business management platform combining CRM, invoicing, scheduling, project management, and document handling. The 1.0.0 spec exposes 47 endpoints across invoices, accounts, contacts, deals, meetings, events, notes, files, activities, and pipelines. Every endpoint authenticates with an api_token query parameter, making it straightforward to embed in serverless functions or no-code workflows.

## For AI agents

Drive a small-business management platform: create invoices, manage CRM contacts and deals, schedule meetings, and attach activities to records.

## Scope

Does not handle payment processing, payroll, or product manufacturing - use for CRM, invoicing, scheduling, and lightweight project tracking inside Agiled only.

## Capabilities

- Create and send invoices with line items and reminders via /invoices and /invoices/{id} endpoints
- Manage CRM accounts, contacts, and deals through full CRUD endpoints under /accounts, /contacts, /deals
- Schedule meetings and event types via /meetings, /events, and /event-types
- Attach notes, files, and activities to deals or contacts via /notes, /files, /activities
- Search across account data with a single POST /search call
- Move deals through pipeline stages tracked by /pipeline endpoints

## Use cases

### Invoicing and Payment Reminders

Generate invoices from completed projects or recurring engagements and trigger reminders against unpaid invoices. The agent calls POST /invoices to create the document and PUT /invoices/{id} to dispatch a reminder. Suitable for freelancers and small agencies running their billing through Agiled.

Example prompt: POST /invoices with the line items for project 42, then PUT /invoices/{id} to send a reminder if status is unpaid after 14 days

### CRM and Pipeline Management

Maintain a clean book of business by syncing leads from web forms or marketing tools into Agiled accounts and deals. The agent uses POST /accounts and POST /contacts to create records, then POST /deals to attach an opportunity in the right pipeline stage. Useful for solo operators and small teams that consolidate CRM with billing in one platform.

Example prompt: On a new lead form submission, POST /accounts, POST /contacts linked to that account, then POST /deals at stage 'New'

### Scheduling and Activity Logging

Coordinate discovery calls and project meetings via POST /meetings while logging activities and notes against the linked deal. The agent ties the meeting outcome back to /activities and /notes so the deal record stays current. Suited for sales-led service businesses where every call should leave a paper trail.

Example prompt: POST /meetings for a 30-minute slot tomorrow with contact 88, then POST /activities with type='call' linked to deal 12

### Agent-Driven Back-Office Automation

Run a Jentic-connected agent that watches inbox events or webhook triggers and writes the appropriate Agiled records - invoice, deal, contact, or note - without human routing. The agent searches Jentic for each operation, loads schemas, and chains calls. This replaces hand-coded back-office scripts for solo operators.

Example prompt: When a new contract is signed, create the contact, create the deal at 'Won', generate the first invoice, and post a note linking the artefacts

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /invoices | Create a new invoice |
| PUT | /invoices/{id} | Send a payment reminder for an invoice |
| POST | /accounts | Create a CRM account |
| POST | /contacts | Create a contact |
| POST | /deals | Create a deal |
| POST | /meetings | Schedule a meeting |
| POST | /search | Search across account data |

## Key resources

- **Invoices** — Create, list, update, and delete invoices; trigger payment reminders
- **Accounts** — CRM company records with full CRUD
- **Contacts** — Individual contacts linked to accounts and deals
- **Deals** — Sales opportunities tracked through pipeline stages
- **Meetings** — Scheduling endpoints for calls and events
- **Activities** — Activity log entries attached to deals or contacts
- **Files** — File uploads attached to records

## Why Jentic

- **Setup:** Wiring the Agiled API by hand means appending its api_token as a query parameter and coding your own logic across invoices, contacts, deals, and meetings. Through Jentic you install once, import the Agiled API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Agiled puts the invoice id in the URL path for updates (/invoices/{id}), while creating accounts, contacts, deals, and meetings takes input in the body, so a rule can pin the agent to a specific invoice or limit it to the create operations it needs. You choose which operations are in the allowed set, so anything you leave out is not reachable.
- **Credential handling:** Your Agiled api_token is stored once, encrypted, by your own Jentic One instance and appended as the api_token query parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an invoice' or 'add a CRM contact', and Jentic returns the matching Agiled operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot CRM Contacts** — CRM-only platform with deeper marketing and service tooling
- **Stripe API** — Payment processing layer for invoices generated in Agiled
- **Asana API** — Project management layer for delivery work tracked against Agiled deals

## FAQ

### Why is there no official OpenAPI spec for Agiled API?

Agiled does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Agiled 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 Agiled API use?

Agiled uses an api_token passed as a query parameter on every request (apiTokenQuery scheme). Through Jentic the token sits in the credential vault and is appended at execution; agents never see the raw value.

### Can I create an invoice and send a reminder with the Agiled API?

Yes. POST /invoices to create the invoice with its line items, then PUT /invoices/{id} (the reminder route) to dispatch a payment reminder to the client. The two calls are separate so reminders can run on a schedule.

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

Agiled does not publish a documented per-second rate limit. The platform throttles abusive bursts at the network layer; agents should retry-with-backoff on 429 responses and serialise high-volume operations across accounts and contacts.

### How do I create a deal and attach a contact through Jentic?

Use the Jentic search 'create an agiled deal'. Jentic returns POST /deals; load its schema, supply contact_id and account_id, and execute. The deal is created at the default pipeline stage and linked to the contact in the same call.

### Does Agiled expose a global search across CRM data?

Yes. POST /search accepts a search term and returns matching accounts, contacts, deals, and invoices in one response, which is useful when an agent only has a partial reference and needs to disambiguate before acting.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Agiled operations and credentials the agent may use. You can pin the agent to a specific record by allowing only the update route that carries the id in its path, such as PUT /invoices/{id}, or restrict it to just the create operations it needs like POST /accounts, POST /contacts, or POST /deals. Any operation you leave out of the allowed set is not reachable by the agent.