.png)
The iplicit API has several available end-points or WKEPs (well known end-points) that can trigger different actions within the iplicit app. These sometimes are referred to as API calls. The base URL is paired with these end-points in order to trigger the actions on the data within the iplicit app.
There are 5 types of actions that can be done with the API: fetch (GET), create (POST), update (PATCH), delete (DELETE), and add (PUT).
The iplicit API can use the actions mentioned above to manage the following:
Please not these links are for the API version 1.11 (latest version).- Attachment
- BankTransaction
- BatchPayment
- Catalog
- Contact
- ContactAccount
- ContactGroup
- CostCentre
- Department
- Document
- DocumentAttachment
- DocumentBatch
- DocumentType
- Enquiry
- LegalEntity
- Payment
- Product
- ProductPurchasePrice
- ProductSalePrice
- Profile
- Project
- PurchaseInvoice
- PurchaseOrder
- Receipt
- Resource
- SaleInvoice
- SaleOrder
- SaleQuote
- Session
For more information on how to use each of them please see the iplicit API Guide and the latest version of the API Reference (Swagger UI) for the tags, headers, etc.
The API version is determined by the version of the target iplicit environment, and this API version should be included in the response body when creating an API session. The target environment should be specified using the Domain header.
The currently active versions are listed in the table below with links to version specific documentation.
| Version | API Reference | OpenAPI Specification |
| v1.11 | API Reference | iplicit API 1.11 |
| v1.10 | API Reference | iplicit API 1.10 |
_______________________________________________________________________________________