ARI API · unofficial, by Cotlet

Create your own ARI API

ARI: no public API or developer docs found on ari.app (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your ARI account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in ARI session and returns only what your login can see.

Try it free now

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by ARI. ARI is a trademark of its owner. If ARI's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/appointments-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-20"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/appointments-for-day";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ date: "2026-11-20" }),
});
const { data } = await res.json();
Python
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
    "https://cotlet.dev/api/v1/custom/appointments-for-day",
    headers={"Authorization": f"Bearer {key}"},
    json={"date": "2026-11-20"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "time": "08:00",
      "client": "J. Rivera",
      "vehicle": "2018 Honda Civic",
      "job": "Front brake pads",
      "status": "confirmed"
    },
    {
      "time": "09:00",
      "client": "D. Chen",
      "vehicle": "2020 Ford F-150",
      "job": "Pads and rotors",
      "status": "confirmed"
    }
  ]
}

01 Build

How do you build an ARI endpoint with Cotlet?

  1. Sign in to ARI in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List tomorrow's appointments with the client, vehicle and job."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a date or a vehicle, and the fields it returns.

  4. Call it with your Cotlet API key.

    Each endpoint gets its own address, POST https://cotlet.dev/api/v1/custom/<name>. You send JSON in and get JSON back, from the same signed-in ARI session.

02 Endpoints

Example endpoints you could build for ARI

Cotlet ships no fixed list of ARI endpoints. You decide which endpoints you build and what each one returns.

  • POST /api/v1/custom/appointments-for-day

    Appointments for a day

    Time, client, vehicle and job of each appointment

  • POST /api/v1/custom/open-job-cards

    Open job cards

    Job cards still in progress, with vehicle and status

  • POST /api/v1/custom/unpaid-invoices

    Unpaid invoices

    Invoices still open after the days you name

  • POST /api/v1/custom/vehicle-history

    Vehicle history

    Past job cards and invoices for one vehicle

  • POST /api/v1/custom/book-appointment writes

    Book an appointment

    A new appointment for a client, vehicle, job and time

A call to an endpoint you built could look like this:

Request

curl -X POST "https://cotlet.dev/api/v1/custom/appointments-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-20"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "time": "08:00",
      "client": "J. Rivera",
      "vehicle": "2018 Honda Civic",
      "job": "Front brake pads",
      "status": "confirmed"
    },
    {
      "time": "09:00",
      "client": "D. Chen",
      "vehicle": "2020 Ford F-150",
      "job": "Pads and rotors",
      "status": "confirmed"
    }
  ]
}

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

What can you use your ARI endpoints for?

  • Schedule Cotlet endpoint Shop chat

    Tomorrow's board for the techs.

    Appointments and open job cards sent to the shop chat every evening.

  • Website form endpoint appointment

    Booking requests from your website.

    A request form on your site books the client into a free slot.

  • Schedule endpoint Google Sheets

    A weekly numbers sheet.

    Unpaid invoices and open job cards pulled into Google Sheets.

  • Voice agent endpoint vehicle history

    Your own phone assistant.

    A voice agent that reads a vehicle's last visit before it answers a caller.

04 Access

What can an endpoint see and change?

An endpoint works in your own ARI session, so it can read and change only what your ARI login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as booking an appointment, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

05 Official API

Does ARI have an official API?

ARI: no public API, developer docs or webhooks were found on ari.app (checked 20 Nov 2026). ARI's integrations page lists built-in partners such as PartsTech and QuickBooks, and its reports page offers CSV downloads of shop data. The full picture with sources: Does ARI have an API or MCP server?

Want ChatGPT or Claude to work in ARI instead of code? See the ARI MCP server.

06 Pricing

What does it cost?

per successful call
10 credits
when a call fails
0
in the smallest pack
≈ 500 calls
free trial, no card
7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

ARI API with Cotlet: questions

Is this an official ARI API?

No. Cotlet is independent and not affiliated with ARI. The endpoints you build run in your own signed-in ARI account.

Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

What happens when ARI changes its screens?

An endpoint works while ARI works the way it did when you built it. If ARI changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

Build your first ARI endpoint

Sign in once, do the job with your agent and save it as an endpoint.

Try it free now

No card. Takes about 5 minutes.