Akazte REST API

Name: Akazte REST API API
Brand: Akazte REST API
Availability: InStock

★ Only Publicly Available SpecCRMDeal Pipelinebearer16 EndpointsREST

For Agents

Create and list customers, leads, invoices, estimates, expenses, and tasks across a self-hosted Akazte CRM, with bearer-token auth scoped to your domain.

Quickstart

Get started with Akazte REST 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 invoice in a self-hosted CRM"

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

Capabilities

What an agent can do with Akazte REST API API.

List customers and create new customer records

Create contacts attached to a customer

Capture leads in the pipeline with structured payloads

Issue invoices, estimates, credit notes, proposals, and contracts

Record expenses, payments, and timesheet entries

GET STARTED

Start building with Akazte REST API API

Explore with Jentic

View OpenAPI Spec

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

Jentic publishes the only available OpenAPI specification for Akazte REST API, keeping it validated and agent-ready. Akazte is a self-hosted CRM and project workflow platform — the JSON REST API exposes 16 endpoints covering customers, contacts, leads, invoices, estimates, credit notes, proposals, contracts, items, expenses, payments, payment modes, timesheets, tasks, and staff. Each Akazte instance runs on the customer's own domain, so the base URL is templated as https://{domain} and bearer-token authentication is required.

Use Cases

Patterns agents use Akazte REST API API for, with concrete tasks.

★ Lead intake and qualification

Wire a marketing form or chatbot directly into Akazte by calling POST /api/leads with the captured details. The agent can then convert qualified leads into customers via POST /api/customers, attach contacts, and follow up with proposals or estimates.

POST /api/leads with the form payload, then POST /api/customers when qualified and POST /api/proposals to send a proposal

Invoice and payment workflow

Automate the back end of a sales process — issue an estimate, convert it to an invoice, record payments against it, and issue credit notes when refunds are due. Each step is a single Akazte endpoint, so an agent can drive the lifecycle without touching the UI.

POST /api/estimates, then POST /api/invoices when accepted, and POST /api/payments to record the customer's payment

Project tracking and timesheets

Track project work by creating tasks, assigning them to staff, and logging timesheet entries against them. Useful for a project-management chatbot that lets staff log time without opening the dashboard.

POST /api/tasks with title and assignee, then POST /api/timesheets with the task id and hours worked

AI agent integration via Jentic

An agent uses Jentic to discover Akazte's CRM operations by intent and execute them through the Jentic vault — useful in environments where the bearer token must not leave a controlled vault, especially since Akazte runs on the customer's own domain.

Search Jentic for 'create an invoice in a self-hosted CRM', load the Akazte POST /api/invoices operation, and execute against the customer's domain

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/api/customers

List customers

POST

/api/customers

Create a customer

POST

/api/leads

Create a lead

POST

/api/invoices

Create an invoice

POST

/api/estimates

Create an estimate

POST

/api/payments

Record a payment

POST

/api/tasks

Create a task

GET

/api/customers

List customers

POST

/api/customers

Create a customer

POST

/api/leads

Create a lead

POST

/api/invoices

Create an invoice

POST

/api/estimates

Create an estimate

POST

/api/payments

Why though Jentic?

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

Credential isolation

Akazte bearer tokens and instance domain values are stored encrypted in the Jentic vault. Agents receive scoped execution capabilities — neither value enters the agent's prompt.

Intent-based discovery

Agents search by intent (e.g., 'create an invoice in a CRM') and Jentic returns the Akazte POST /api/invoices operation with its schema so the agent calls it without browsing docs.

Time to first call

Direct Akazte integration: a day to wire bearer auth, the templated domain, and per-resource flows. Through Jentic: well under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Zoho CRM

Hosted CRM with deeper deal-pipeline features.

Choose Zoho when you want a hosted, mature CRM with a large API surface; choose Akazte when self-hosting on your own domain matters.

Alternative

Salesforce

Enterprise CRM with the largest API surface in the category.

Use Salesforce in enterprise contexts; use Akazte for lightweight self-hosted setups.

Complementary

Stripe

Run the actual card charge — Akazte records the payment, Stripe processes it.

Pair Stripe with Akazte when an agent collects payment via Stripe and writes the record into Akazte for the books.

FAQs

Specific to using Akazte REST API API through Jentic.

Why is there no official OpenAPI spec for Akazte REST API?

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

Akazte uses HTTP bearer authentication — supply the token in the Authorization: Bearer <token> header. Through Jentic, the bearer token and your Akazte domain are both stored in the encrypted Jentic vault and injected at execution time.

Does the Akazte API run on a fixed base URL?

No. The base URL is templated as https://{domain} and resolves to your specific Akazte instance. Replace {domain} with your live Akazte URL when configuring credentials. Jentic stores your domain alongside the bearer token so calls route correctly.

How do I create an invoice in Akazte through Jentic?

Use the Jentic search query 'create an invoice in Akazte'. Jentic returns the POST /api/invoices operation; supply the customer id and line items and Jentic injects your bearer token and domain at execution.

Can I capture leads from a chatbot via Akazte?

Yes. POST /api/leads accepts a structured lead payload and creates a record in your CRM pipeline. From there, an agent can convert qualified leads to customers via POST /api/customers.

Are there rate limits on the Akazte API?

Akazte runs on your own domain so rate limits depend on your hosting capacity. The OpenAPI spec does not declare them. Implement basic backoff on 429 or 5xx responses for safety.