Changing, deleting and adding records
This interface allows individual or multiple records in the search database to be updated, deleted or added. It should be noted, however, that changes may be lost when a data import is performed via this interface. The product data export provided by your shop system is always used as the basis of the import. Therefore only use this interface temporarily to make a quick correction to a record.
All changes are immediately available in the search. By saving the database the changes made will be written to the hard drive, so that the changes will also be available after a restart. The saving process requires processing power, however, so it should not be carried out for every change call.
REST Interface
FACT-Finder 7.3 adds a REST-API. The search application contains the technical documentation and can be accessed via this URL:
$stringEscapeUtils.escapeHtml($body)The interface offers not only the parameter documentation, but also the option to test a query and review the result. The documentation was created with Swagger, you can use Swagger Codegen to generate a client for it and use it for your code.
The methods are documented under records.
HTTP Interface
Each of the update methods is invoked using a different URL:
$stringEscapeUtils.escapeHtml($body)In the id parameter you must indicate the record ID of the record that should either be deleted or updated. If it is a new article, this parameter will cause a new ID to be generated in the database.
If you want to update or create an article, you must send its fields as parameters. For this purpose, the parameter name is the field name and the parameter value the associated field value.
If save=true is sent as a parameter, the database will also be saved after the change. If the database persistence is not ensured by saving, changes would be lost when restarting a server or the application. Please note, however, that no searches can be conducted while the database is being saved, and this may cause delays to the search process. We therefore recommend that you do not pass the parameter with every call, but define it as dependent on the time of day or number of changes that have been applied.
Webservice/SOAP Interface
End of Life
Please note: the SOAP interface will no longer be updated or upgraded. We recommend the REST-API for new customers. If you have been using the SOAP interface so far, you can go on using it. We do however recommend changing your integration interface to improve performance.
The WSDL of this interface is identical with that of the import interface, but here the methods insertRecord, insertRecords, deleteRecord, deleteRecords and updateRecord are used.
All methods send the channel name, the login data and the save flag. The delete methods will also send either an ID or a list of IDs that are to be deleted. Furthermore, the update and addition methods have one or more ImportRecord objects.