Connecting Caspit (כספית) to AI and Automation via Its REST API

If you run your bookkeeping in Caspit, you don't need to export CSVs by hand to get value from AI. Caspit exposes a real REST API that lets external software read and write your documents, customers, products and payments programmatically. The work isn't calling an AI model — that part is easy and commoditized now — it's building the reliable layer between Caspit and whatever you want to automate.

How the Caspit API actually works

Authentication is token-based. You POST your credentials to the token endpoint and get back a short-lived access token that you attach to every subsequent call. Two details matter in practice and trip up most first integrations: the token lives on a sliding 10-minute window, so a long-running job has to refresh it; and the token is scoped to a single business, so a multi-business account needs a separate token per Osek/business.

POST https://app.caspit.biz/api/v1/Token
Content-Type: application/json

{
  "UserName": "...",
  "Password": "...",
  "OsekMorsheNumber": "...",
  "BusinessId": "..."
}

=> "B0D18327C19E8AED..."  // valid 10 min, sliding, per-business

From there the API is straightforward REST over JSON. You get roughly twenty business objects to work with, including the ones most automations need:

• Documents — create, modify and cancel invoices, receipts and invoice-receipts (the core of any billing automation).
• Customers and suppliers — read and write contacts, plus contact balance reporting.
• Products — the catalog and catalog-number lookup, so AI can match free-text to real SKUs.
• Payments and expenses — pull expense payments for a given period for reconciliation.
• Credit-card charging — charge a saved card token, and set up pre-authorized recurring debits.
• Hashavshevet export — generate the accounting file format your bookkeeper expects.

Lists come back paginated (page / pageSize), so any sync that reads history has to loop through pages rather than assume one response. There are also webhook event types referenced in the API, which means for some events you can be pushed a notification instead of polling — though in practice many integrations still poll on a schedule for reliability.

What you can actually build

1. Inbox-to-invoice: an AI reads incoming supplier emails or photographed receipts, extracts vendor, amount and VAT, and files the expense in Caspit automatically — no manual typing.
2. WhatsApp billing assistant: a customer asks 'what do I owe?' on WhatsApp; the bot pulls their live contact balance and open documents from Caspit and answers in plain Hebrew, then sends a payment link.
3. Smart reconciliation: nightly, pull the period's documents and payments, and let AI flag mismatches, duplicate invoices or unpaid debts that are aging — a one-line summary in Slack each morning.
4. Auto-categorization: when a document is created, AI classifies it to the right transaction code / accounting category before it ever reaches your bookkeeper, cutting month-end cleanup.
5. Recurring revenue on autopilot: combine the customer record with credit-card tokens and pre-authorized debits to charge subscriptions and issue the matching receipt in one flow.

No-code vs. custom code — the honest tradeoff

Caspit doesn't have a polished, native connector in Zapier or Make the way the big global tools do. You can still drive it from those platforms using a generic HTTP module, but you'll be hand-managing the token refresh, the pagination and the JSON shapes inside a visual builder — which gets brittle fast. For a low-volume, single-step flow that's fine. The moment you have real volume, money movement (charging cards), private financial data that shouldn't pass through a third-party cloud, or genuinely complex logic, you want a small custom service that owns the API properly.

With Caspit the AI is never the hard part. The 10-minute sliding token, the per-business scope and clean data mapping into your books — that's the engineering.

If you're a business owner or bookkeeper searching for a developer to connect Caspit to AI and automations, this is exactly the kind of integration I build — end to end, with the boring reliability around the edges done right so your numbers stay correct. Tell me what you wish happened automatically in your books, and I'll tell you honestly whether it's a weekend job or a real project. The contact form below reaches me directly.