Magento 2.1.9 - Can not acces Magento API log file. Details are available in Magento log file. Report ID: webapi-5b7e549729324

Magento 2.1.9 - Can not acces Magento API log file. Details are available in Magento log file. Report ID: webapi-5b7e549729324

August 11, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento 2.1.9 - Can not acces Magento API log file. Details are available in Magento log file. Report ID: webapi-5b7e549729324

Solving Magento API Log File Access Issues

Are you facing difficulties accessing your Magento API log files? You’re not alone! In this post, we’ll troubleshoot the “Internal Error” message you’ve been encountering while trying to access order data via the REST API.

Understanding the Error Message

When you send a GET request to /rest/V1/orders with a search criterion for an increment ID, you receive the following error:

{
    "message": "Internal Error. Details are available in Magento log file. Report ID: webapi-5b7e549729324"
}

This message indicates that there’s an internal issue with your API processing, and more information can be found in the log files generated by Magento.

Checking the Log Files

To access these log files, you typically look for them in the var/report/api directory of your Magento installation. However, as you pointed out in your question, this folder doesn’t seem to exist.

Creating the API Report Directory

If the var/report/api folder isn’t present, it’s likely because no API errors have been logged that would require a report file. To create this folder manually:

  1. Navigate to your Magento installation directory via SSH or SFTP.
  2. Locate the var/ folder.
  3. Inside the var/ folder, create a new folder called report/.
  4. Within the report/ folder, create another folder named api/.

After creating these folders manually, they should be ready to receive log files when an API error occurs.

Configuring Error Reporting

If you’re still not seeing any log files in the var/report/api folder after encountering the “Internal Error” message, it might be due to incorrect error reporting settings in Magento.

Enabling Log Files for API Errors

To ensure that API errors are properly logged:

  1. Open your Magento installation’s app/etc/config.php file.
  2. Find the error_reporting setting and make sure it is set to a level that includes the E_ERROR constant, such as E_ALL.
  3. Save the changes and clear the cache.

With these settings, Magento should generate log files for API errors in the var/report/api folder you created earlier.

Troubleshooting Common API Issues

If your increment_id search isn’t working as expected, it might be due to one of the following common issues:

  1. Invalid Search Field: Ensure that you’re using the correct field name for your search criterion. In this case, increment_id is likely not recognized by Magento’s default search filter.

  2. Incorrect API Endpoint: Double-check that you’re sending requests to the appropriate endpoint. The V1 version number in the URL is correct as of current stable releases, but double-check it matches your installation’s version.

  3. Insufficient Permissions: Verify that the user account making the API request has sufficient permissions to access order data.

Conclusion

Accessing Magento API log files can be challenging at first, but with the right configuration and troubleshooting steps, you’ll be able to diagnose and resolve issues efficiently. Remember to:

  • Manually create the var/report/api folder if it doesn’t exist.
  • Configure error reporting to ensure proper logging of API errors.
  • Double-check your search criteria, API endpoints, and user permissions.

If you’re still encountering difficulties or need further assistance with Magento API development, consider exploring our comprehensive guides on Magento REST API integration for more in-depth insights and best practices.

Magento 2 Magento 1 API Configuration

Our network