Troubleshooting Centre
MikroAPI 401 Licence and MAG Warning: A Diagnostic Checklist
Distinguish a MAG or licence warning in a MikroAPI 401 response from an invalid API key; follow safe checks, support and restart steps.
If a MikroAPI response contains a licence or MAG service warning, first identify the condition reported rather than changing the password. In Mikro's licence response documentation, this is described under model number 401-05. This number is not a separate HTTP status code; in the example response body, StatusCode is 401 and IsError is true.
First check: separate the HTTP response from the application error
In an authorised environment, record the failed request's time, HTTP status and sanitised error message. Check whether the body contains a licence or MAG warning, an invalid key message, or something else. Do not apply one solution to every case based only on “401”. Do not include API keys, passwords, company data or the full request body in screenshots or support emails.
| Observed condition | Low-risk check | Next step |
|---|---|---|
| Licence or MAG service warning | Compare service validity with authorised records for the correct company and product | Confirm with a Mikro solution partner or the person responsible for licensing |
| Invalid API key message | Check whether the application reads the key for the correct environment; do not print the value | Verify API access settings with an authorised person |
| No response received | Check whether the request reaches the API service | Contact the network or service owner; do not assume a licensing issue |
Which licence and service details should be verified?
The official error description refers to the validity of the MAG service for a purchased product, or the service period for a rented product. Verify the customer's product family, version, company or working year and API access configuration together. This guide does not assume a renewal fee or that the same licence is sufficient for every installation; the authorised provider confirms current terms.
How do you confirm the issue is resolved?
- After an authorised person corrects access or service status, perform one authorised read operation in a test environment without changing any data.
- Check the application's error field and the expected returned data as well as the HTTP status.
- List the pending jobs. A successful read does not prove that earlier orders were processed.
- Before restarting the write queue, compare external references with ERP records. Do not blindly resend an order whose outcome became unknown after a timeout.
Example scenario: Three orders are waiting in the dealer portal; the response to one was lost. When access returns, first check whether that order exists in the ERP. If no match is found and a reliable query cannot be performed, send the job for human review. Other jobs also run with bounded retries; do not create a continuous request loop for a licensing error.
When should you request support?
If the warning persists after the correct company and environment are confirmed and an authorised person verifies that the service is valid, contact product support. The product and API version, sanitised error text, time and checks performed provide a useful starting point. Disabling security controls or writing directly to ERP tables is not recommended as a solution to this warning.
For the integration as a whole, review the Mikro ERP dealer portal guide and its decisions on data ownership and order acceptance.
Sources and verification
The checklist and scenario are architectural suggestions, not claims of testing in a real customer environment or of a manufacturer partnership. Technical sources checked: 17 October 2026.
Address recurring integration problems
Once licensing and access responsibilities are clear, explore custom software development for queues, error tracking and deduplication for more information.
Let's discuss your needs →