Supplier API
Written by Endre Sletvold
Updated over a week ago


The supplier API will make customers and integration partners able to update and maintain the directory of suppliers in Qondor. The API offers standard put, post and get operations, in addition to specific operations for maintenance via external references, which makes it easy to synchronize the supplier catalog in Qondor with external supplier databases, such as CRM systems etc.


The following operations are available in the supplier API:

Insert Supplier

This is a POST operation, and enables supplier API consumers to create suppliers in Qondor. The operation accepts JSON form data. For a detailed description of the operation, please see the Supplier API --> Insert supplier in the Qondor API documentation. Notice the External reference field, which can be used to refer to the supplier in other systems, so that these can more easily be kept up to date across databases and systems.

Update Supplier

Works much like the Insert Supplier operation, but is a HTTP PUT method. This operation requires you to provide either the identifier or the external reference of an existing supplier in Qondor. For a detailed descripiton of the operation, please see the Supplier API --> Update supplier in the Qondor API documentation.

Delete Supplier

There are two methods for deleting suppliers in Qondor. Both are HTTP DEL operations, and differ from each other in that one deletes a supplier by using the suppliers identifier, while the other identifies the supplier and deletes it by using an external reference. Note that these have different urls. For a detailed description of both, please see the Supplier API in the Qondor API documentation. Documentation of deletion using the suppliers identifier can be found in the Supplier API --> Delete supplier, and deletion with an external reference can be found in Supplier API --> Delete supplier by external reference.

Get Supplier(s)

This can be done in several ways, and with three methods which are all HTTP GET operations. You can either retrieve a single supplier with an external reference, or you can do it with an identifier (click on the links to go to the documentation for the operations). Alternatively, you can retrieve all suppliers to which the API user has access. This method also supports retreiving suppliers for a specific office by submitting the office identifier as a query parameter. Please see the Supplier API --> Get all suppliers in the Qondor API documentation for more details.

Note that if you already know the identifier or the external reference of the supplier you want to retreive, one of the single supplier get methods should be used.


The operations described above will essentially enable API consumers to perform most of the tasks required to keep qondor's supplier directory up to date. However, there is one more API that is relevant for operations linked to suppliers, and that is the contact person API.

Contact persons are used in several contexts in Qondor. For example, both suppliers and customers have contact persons, so operations on these are at a separate endpoint. The contact person API contains the necessary insert, update and delete operations to keep Qondor's contact persons up to date, but the operation that is particularly relevant for suppliers is the Update Supplier Relation method. This method links a contact person to a supplier. To find documentation for this specific operation, please see the Contact person API --> Update supplier relation in the Qondor API documentation. For an overview of the contact person API and its operations, please see the Contact person API --> Create contact person in the Qondor API documentation.


For you to be able to use Qondor's supplier API, you must be added as a registered user and granted access to every API you want to use. The overall access to the data is based on access tokens. Take a look at the API Introduction article for more information on how to use the API.

Reach out to your Qondor contact person or Qondor Support for requests regarding access and usage of the API.

Did this answer your question?