Skip to content

System and API integration: devices, documents, email and ERP Software connected to the real world

ANTASY IT (a.it) connects business software to what surrounds it: ZKTeco and Hikvision attendance devices, AI reading of supplier invoices, email approval workflows, online stores and third-party APIs. We build each connection, then run and monitor it, because an integration that silently stops is worse than none.

Connected
Attendance devices · AI document reading · Email
Protocols
REST · Webhooks · WebSockets · ISAPI · ZK/TCP
Running at
Facturty (our product) · Damak group
Last reviewed

Time clocks, readers and devices: we connect them to your software.

Fingerprint time clock
Photo: generic device (Pexels), not client equipment.

Overview

What is system integration, and when do you need it?

System integration makes separate systems exchange data without anyone retyping it: a terminal sends attendance to an HR app, a scanned invoice fills a purchase entry, an online order reaches the ERP. You need it when the same information is copied by hand between tools. ANTASY IT builds these connections and keeps them running.

The cost of a missing integration is easy to miss because it is spread out: ten minutes a day retyping supplier invoices, a weekly export of attendance into a spreadsheet, an order copied from a store’s back office into the ERP. Each copy is a chance for an error that someone finds weeks later.

An integration removes the copy. The hard part is rarely the first transfer; it is what happens on the day the device is offline, the API answers with an error, or the document is not quite what was expected. That is where most of our work goes.

What we have connected

What have we already connected?

Four kinds of integration are in production. Two of them, attendance and email governance, are described without naming the client, with their features as published.

  • ISAPI · ZK/TCP

    Attendance devices

    Hikvision and ZKTeco terminals on several sites feeding a web HR app: arrivals, exits, lateness, anomalies and hours, with each device’s live status. See biometric attendance.

  • Mistral Pixtral

    AI document reading

    In Facturty, a photographed supplier invoice is read by a vision model and pre-fills a purchase invoice that a person checks before saving. See invoicing modules.

  • Approval workflow

    Email governance

    A layer over company email: external messages in and out wait for approval, every decision is kept in a searchable history, and administrators oversee all mailboxes.

  • Damak group

    Online platform and ERP

    The tyre group’s online platform and the ERP that runs orders, deliveries, invoices and payments, built by us as one system. See B2B portals.

Mohamed Damak et Cie

Tyre import and distribution, since 1967 · Sfax and Tunis

The group’s online platform and the ERP behind it, built as one system: orders, deliveries, invoices and payments, with prices and access depending on the customer segment.

What we builtVisit site ↗ (opens in a new tab)

our product

Facturty

Billing and back-office software

Supplier invoices read by Mistral’s Pixtral vision model, then shown in an editable form where line amounts and totals are recalculated before a person saves the purchase invoice.

How we build

How do we build integrations that keep working?

Six rules we apply to every connection, whatever the protocol.

  1. Start from real samples

    Documentation describes what a system should send. A day of real events, real invoices or real API answers shows what it actually sends. We collect both before writing the connector.

  2. Give every event an identity

    An attendance punch, an order or a document is recognised by its own identifiers, so reading it twice never counts it twice.

  3. Catch up after an outage

    The connector remembers the last item it stored and resumes from there when the other side comes back, instead of losing what happened in between.

  4. Never trust outside data blindly

    Everything is validated before it is written. AI output is a proposal: in Facturty, totals are recomputed from the lines and a person confirms.

  5. Keep secrets and devices private

    Keys and passwords stay on the server, never in the browser. Devices are reached through the network path agreed with your administrator, and their addresses never appear in screenshots or documents.

  6. Watch it in production

    Errors and silences are monitored like the rest of the application. See DevOps and hosting.

Email governance

Can company email require approval before it goes out or comes in?

Yes. ANTASY IT has built a governance layer over company email in which external messages, inbound and outbound, wait for approval before delivery. Every message keeps its decision (approved, rejected or automatic) in a searchable history, with an audit trail per sender and per recipient, and administrators oversee all mailboxes.

This kind of control suits companies that must prove what left the building and when: documents sent to customers, offers, files shared with third parties. The approval rules, who approves and what is approved automatically are decided with you; the history is what makes the system useful months later.

How we deliver

How does an integration project run?

Five stages, each ending with something you can check. Durations are agreed once both sides are known.

  1. 01

    Map

    Both systems, their interfaces, their owners and what must flow in which direction.

  2. 02

    Sample

    Real data from each side: events, documents, API answers, including the odd ones.

  3. 03

    Build

    The connector, its validation rules and its catch-up logic, on a test copy.

  4. 04

    Test on real data

    A real day replayed end to end, compared with what people recorded by hand.

  5. 05

    Run

    Hosted, monitored and updated when either side changes.

Stack and limits

Which technologies, and what have we not connected yet?

We work with what the other system offers: REST APIs, webhooks, WebSockets for live screens, vendor interfaces such as Hikvision ISAPI and the ZKTeco protocol, and AI models through their APIs.

In production

  • REST
  • Webhooks
  • WebSockets
  • ISAPI
  • ZK/TCP
  • Mistral API
  • SMTP

Not claimed until it runs

Two kinds of integration are not listed here: online payment gateways, because the stores we run take cash on delivery, and e-invoicing platforms such as El Fatoora, because our work there has reached the invoice file format, not the connection (see invoicing modules). Both are possible; neither is listed as done before it runs.

FAQ

System integration questions

Can you connect our ERP to a third-party API?

Usually, yes, as long as the other system offers an interface: a REST API, webhooks, a file exchange or a database we are allowed to read. We start from its documentation and a set of real answers, then build a connector with validation, retries and catch-up, and monitor it once it is live.

What happens when the other system is down?

Nothing should be lost. We build each connector to remember the last item it stored and to resume from there when the other side returns, and every item has an identity so a second read never creates a duplicate. Long silences are treated as incidents, not as quiet days.

Is AI document reading done on your servers or by an external service?

By an external service. Facturty sends the invoice image to Mistral’s API, where the Pixtral vision model reads it and returns structured data. We say so because it matters for confidentiality: if your documents must not leave your servers, we discuss other options before building anything.

Do you use webhooks or regular polling?

Whichever the other system supports reliably. Webhooks deliver events as they happen; polling asks at intervals and is often the only option with devices. In both cases the connector stores where it stopped, so a missed webhook or an interrupted poll is recovered rather than lost.

Who maintains the integration when the other side changes?

We do, when we host and maintain the application. Connectors are monitored like the rest of the system, so a changed API usually shows up as an error before anyone notices missing data. The fix is then planned like any other change to the software we run for you.

What access do you need to connect our systems?

Ideally a test environment or a test account on each side, plus the interface documentation. When only production exists, we start by reading real samples without writing anything, and agree with you on when writes may begin. Keys and passwords are kept on the server, never in the browser or in shared documents.

Two systems that should talk? Tell us which

Name the systems, the data and the direction. We answer with what each side offers and what we would need to see.