What are the available iplicit APIs?

This article covers the iplicit API - the connection that lets other systems talk to iplicit and read or update your data. It explains what the API can do in general terms. For getting set up, see 'How do I create an API key'.

---

What the iplicit API is for

An API is a way for two different pieces of software to exchange information without a person clicking through screens. Think of it like a waiter: your system places an order, the iplicit API carries it through, and iplicit sends the result back. Businesses use the iplicit API to connect other tools – such as a CRM, an e-commerce platform, or a custom in-house system - so data moves automatically instead of being typed in twice.

---

What you can do through the iplicit API

The iplicit API covers most of the records you'd normally create or view inside iplicit itself - things like sale invoices, purchase orders, bank transactions, contacts, and documents. Each of these is called an endpoint. The full, up-to-date list of every endpoint is maintained at docs.iplicit.com/api rather than here, so you're always looking at the current version.

---

The four actions the iplicit API supports

Every request you send to the iplicit API does one of four things:

1. Fetch (GET) – read existing data, such as pulling a list of purchase invoices
2. Create (POST) – add a new record, such as raising a sale order
3. Update (PATCH) – change part of an existing record, such as amending a due date
4. Delete (DELETE) – remove a record.

You may see these written as HTTP methods in technical documentation – GET, POST, PATCH, and DELETE mean the same as fetch, create, update, and delete above.

---

Where to find technical detail

The iplicit API guide and the Swagger reference list every endpoint with its exact fields and examples. Use these once you know which endpoint you need – this article is the starting point, not the technical reference..