canonical: https://jentic.com/apis/axonaut.com/axonaut # Axonaut API Jentic publishes the only available OpenAPI specification for Axonaut API, keeping it validated and agent-ready. Axonaut is an all-in-one CRM and small-business management platform popular with French SMBs. The v1 API exposes contacts, invoices, quotations, expenses, projects, and opportunities with create, read, and update operations, supporting both sales-pipeline workflows and accounting integrations. Authentication uses an API key passed in the userApiKey header. ## For AI agents Manage Axonaut contacts, invoices, quotations, expenses, projects, and opportunities from one CRM API. Suited to agents that automate quote-to-cash and pipeline tracking for SMBs. ## Scope Does not handle payroll, banking integrations, or HR records - use Axonaut for CRM contacts, opportunities, quotations, invoices, expenses, and projects only. ## Capabilities - Create, list, retrieve, and update contacts in the Axonaut CRM - Issue and track invoices through the /invoices endpoints - Generate and list sales quotations for prospects and customers - Record and list business expenses by category and date - Create and list projects associated with customers and opportunities - Track sales opportunities and pipeline stages via the /opportunities endpoints ## Use cases ### Quote-to-Cash Automation SMB ops teams can automate the path from prospect to invoice by chaining /quotations and /invoices. A signed quote can be converted into an invoice via POST /invoices once accepted, keeping accounting and CRM aligned. Suited to consultancies and agencies that bill against fixed-price quotes. Example prompt: Create a quotation via POST /quotations for a prospect, then on acceptance create an invoice via POST /invoices referencing the same contact ### CRM Contact Sync from Lead Sources Marketing automation tools can push captured leads into Axonaut as contacts via POST /contacts and update them on subsequent enrichment via PUT /contacts/{id}. Pair with /opportunities to create a pipeline entry once the contact is qualified. Useful for unified contact records across acquisition channels. Example prompt: POST /contacts with the new lead's details and create an opportunity via POST /opportunities tied to that contact id ### Expense and Project Tracking Finance teams can log business expenses against categories via POST /expenses and tie work to /projects so cost reporting reflects actual project P&L. The list endpoints support periodic reconciliations against bank or card statements. Suited to professional-services teams running multiple concurrent client engagements. Example prompt: POST /expenses with a categorised business expense and link it to the active project by id for accurate project cost tracking ### Agent-Driven Pipeline Updates via Jentic A revenue-ops agent can refresh contacts, opportunities, and invoices in Axonaut on a schedule via Jentic without holding the userApiKey. Jentic exposes the contact, opportunity, and invoice operations as discoverable tools the agent can chain. Suited to revenue copilots that keep CRM and books in sync. Example prompt: Search Jentic for 'list axonaut opportunities', load GET /opportunities, and execute it to retrieve the current pipeline for a weekly review ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /contacts | List contacts | | POST | /contacts | Create a contact | | GET | /invoices | List invoices | | POST | /invoices | Create an invoice | | POST | /quotations | Create a quotation | | POST | /expenses | Log an expense | | GET | /opportunities | List opportunities | ## Key resources - **Contacts** — Create, list, retrieve, and update CRM contacts - **Invoices** — Issue and list invoices tied to contacts and projects - **Quotations** — Create and list sales quotes for prospects - **Expenses** — Log and list categorised business expenses - **Projects** — Create and list projects linked to clients - **Opportunities** — Track sales opportunities through pipeline stages ## Why Jentic - **Setup:** Wiring Axonaut by hand means placing the key in its non-standard userApiKey header, pointing at axonaut.com/api/v1, and writing your own pagination and back-off across contacts and invoices. Through Jentic you install once, import the Axonaut API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Axonaut exposes a resource id in the URL path for some reads such as GET /contacts/{id}, but creates and updates carry the record in the request body, so scoping is best done by operation. You limit the agent to the operations it needs, such as GET /opportunities or POST /invoices, and the rest are not exposed unless you add them. - **Credential handling:** Your Axonaut user API key is stored once, encrypted, by your own Jentic One instance and injected into the userApiKey header 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 in axonaut' or 'list opportunities', and Jentic returns the matching Axonaut operation with its input schema so the agent calls the right endpoint without browsing the docs. ## Related APIs - **HubSpot API** — HubSpot is a much larger CRM platform competing with Axonaut for SMB sales workflows. - **Pipedrive API** — Pipedrive is a sales-focused CRM with strong pipeline workflows competing with Axonaut. - **Zoho API** — Zoho's broader business suite often pairs with smaller CRMs for accounting or workflow extensions. ## FAQ ### Why is there no official OpenAPI spec for Axonaut API? Axonaut does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Axonaut 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 Axonaut API use? Axonaut uses an API key passed in the userApiKey header. Through Jentic, the key is stored encrypted in the vault and injected into the userApiKey header on every request. ### Can I create invoices and quotations with the Axonaut API? Yes. POST /quotations creates a sales quote and POST /invoices creates an invoice. Both are tied to a contact id so the records stay aligned with the CRM. ### How do I track my sales pipeline through the Axonaut API? Use GET /opportunities to list pipeline entries and POST /opportunities to add new ones. Pair with /contacts and /projects to keep the pipeline tied to the right customer and engagement. ### What are the rate limits for the Axonaut API? The Axonaut OpenAPI spec does not declare published rate limits. Axonaut enforces account-level quotas; back off on 429 responses if encountered when iterating across pages. ### How do I list opportunities through Jentic? Search Jentic for 'list axonaut opportunities', load GET /opportunities, and execute it. Jentic injects the userApiKey header and returns the current pipeline entries to your agent. ### Can I limit what my agent is allowed to do with the Axonaut API? Yes. Because Jentic One is self-hosted, you decide which Axonaut operations your agent can reach, and scoping is done per operation. You can expose only the endpoints the task needs, such as GET /opportunities to read the pipeline or POST /invoices to raise an invoice, while leaving contacts, quotations, expenses, and everything else unavailable unless you add them. Your Axonaut user API key stays with your own instance and is injected into the userApiKey header at execution time, so the agent calls only the operations you allowed.