Good to know
Support & assistance
Hulp bij technische vragen, foutmeldingen en storingen. Lees hoe u ondersteuning aanvraagt, problemen meldt en gebruikmaakt van onze documentatie en helpdesk.
How can I check whether an API integration is working correctly?
A connection may be technically accessible, yet data processing may still not be functioning entirely correctly.
It is therefore advisable to check both the technical connection and the functional results.
For example, check whether API requests are being executed successfully, whether the expected number of records is being processed, and whether the data appears correctly in the target system.
For business-critical processes, monitoring can be set up to automatically detect anomalies.
Regular checks on data quality remain important, even when the data linkage operates largely automatically.
How can I improve the performance of a slow API connection?
A slow connection can be caused by a number of factors, such as large volumes of data, a high number of individual API requests or limited capacity of one of the systems involved.
Start by identifying where most of the processing time is spent.
For example, check the response times of API requests, the amount of data retrieved and any delays between process steps.
Possible improvements include reducing unnecessary data, processing records more efficiently and adjusting the synchronisation frequency.
In complex workflows, logging can help to identify specific bottlenecks.
Can a failed data processing operation be carried out again?
Whether a failed processing operation can be restarted depends on the integration used and the way the process is set up.
In the event of temporary problems, such as a network fault, running the process again may be a suitable solution.
However, it must first be checked whether the original processing actually failed.
It may well be the case that a receiving system has already processed the data, even though the confirmation has not yet been received.
By using unique identifiers and checking against existing records, it is possible to prevent data from being duplicated when a new attempt is made.
Where can I find technical documentation on Clickker and CAS?
For technical information about Clickker and CAS, users can consult the available product documentation and knowledge base.
This includes topics such as installation, system requirements, configuration and frequently asked support questions.
When developing an integration, it is important to use documentation that corresponds to the installed software version and the relevant API functionality.
For Exact-specific API features, you can also consult the official developer documentation for Exact.
Where documentation does not provide sufficient clarity, additional technical support may be required.
Why am I getting an error message when I make an API request?
An API request may fail for various reasons.
Common causes include invalid authentication details, insufficient access rights, missing required fields or an incorrect request format.
It is also possible that an external application may be temporarily unavailable or that an API limit has been reached.
The HTTP status code and any additional error message may help to identify the cause.
When investigating an error, it is important to distinguish between technical connection problems and functional errors in the data supplied.
When is it advisable to seek technical support?
Technical support is particularly important when a problem affects business-critical processes or when data may be processed incorrectly.
Examples include a failure in the order link, missing financial transactions or repeated synchronisation failures.
Specialist support may also be advisable when making changes to authentication, server infrastructure or complex workflows.
Try to gather as much relevant information as possible in advance, such as error messages, timestamps and the applications involved.
This allows the technical analysis to be carried out in a more targeted manner and helps to minimise the impact on business processes.
What can I do if data is no longer being synchronised?
If data is no longer being updated, the first step is to determine when the last successful synchronisation took place.
Next, check whether the relevant systems are accessible and whether the required authentication details are still valid.
Check the available logs to determine whether any errors occur whilst retrieving, processing or sending data.
It may also happen that a data record does not meet the required conditions, which prevents it from being processed.
Once the cause has been resolved, it is necessary to check what data may have been left behind and whether it can be safely processed again.
What should I do after updating Exact or a linked application?
Software updates may affect existing integrations, for example when interfaces, authentication methods or data structures change.
You should therefore check in advance whether the new software version is supported by the interface you are using.
Where possible, read the relevant release notes and test key processes before deploying the update to production.
After the update, it is advisable to check the key data exchanges, such as retrieving customer data or processing orders.
If a problem arises, the exact software versions and the time of the update are important details for the investigation.
What should I do if my Clickker link stops working?
If a Clickker link stops working, it is important to first identify which part of the data exchange is causing the problem.
Check whether Exact is accessible, whether the external application is available, and whether any recent changes have been made to the server environment or configuration.
Next, check the available error messages and log files. These may contain information about connection issues, invalid authentication details or incorrect API requests.
Try to determine whether the problem affects all data exchanges or just one specific operation.
If the problem cannot be resolved independently, a support ticket can be submitted, including the relevant technical information.
What information do I need to provide when submitting a support request?
A clear support ticket helps us analyse technical issues more quickly.
Please specify which applications are involved, what action is being carried out and what the expected result is.
Next, describe exactly what is happening. If possible, include the full error message, the time of the fault and any relevant log data.
Information about recent changes may also be important, such as a software update, a change to an API key or an adjustment to the network environment.
Do not share passwords, secret API keys or access tokens in a standard support ticket.
This information enables the cause of a problem to be investigated in a more targeted manner.