Magento 2 API always returns Consumer is not authorized to access %resources

Magento 2 API always returns Consumer is not authorized to access %resources

July 5, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento 2 API always returns Consumer is not authorized to access %resources

Solving the Magento 2 API Authorization Issue

Are you facing difficulties while using the Magento 2 REST API? You’re not alone. Many developers struggle with the “Consumer is not authorized to access %resources” error message.

Understanding the Problem

You’ve already managed to get an admin token using the integration endpoint:

curl -X POST "http://magento.dev.blackorange.nl/index.php/rest/V1/integration/admin/token" \
-H "Content-Type:application/json" \
-d '{"username":"adminuser", "password":"adminpass"}'

However, when you try to access any other endpoint like products:

curl -X GET -H "Authorization: Bearer TOKEN" "http://magento.dev.blackorange.nl/rest/V1/products"

You hit the wall with the dreaded authorization error.

Why You’re Facing the Issue

The problem lies in how Magento handles token-based authentication and access control. By default, the generated admin token only has access to a limited set of resources.

The Solution: Create a Custom Role

To solve this issue, we need to create a custom role with the required permissions for your API consumer.

  1. Create a new role in the Magento admin panel:

    • Navigate to System > Permissions > Roles
    • Click “Add New Role”
    • Set the name (e.g., “API Consumer”)
    • Save the new role
  2. Assign required privileges:

    • Under the role, click on “Role Resources”
    • Select the resources needed for your API interaction
    • For a basic setup, select “All” under “System” and “All” under “Sales”
    • Save your changes
  3. Create an admin user with the new role:

    • Navigate to System > Permissions > All Users
    • Click on “Add New User”
    • Set the required credentials (e.g., username: apiuser, password: apipassword)
    • Under “Role”, select the previously created “API Consumer” role
    • Save the user

Accessing the API with Custom Credentials

Now, try generating a token using your new API consumer:

curl -X POST "http://magento.dev.blackorange.nl/index.php/rest/V1/integration/admin/token" \
-H "Content-Type:application/json" \
-d '{"username":"apiuser", "password":"apipassword"}'

Replace the URL with your Magento instance and use the apiuser credentials. You should now receive a valid token response.

Testing the API Access

With the new token, try accessing an endpoint:

curl -X GET -H "Authorization: Bearer TOKEN" "http://magento.dev.blackorange.nl/rest/V1/products"

Ensure to replace TOKEN with the actual value from your previous response.

Conclusion

In this article, we explored a common issue faced by Magento 2 developers when using the REST API. By understanding how Magento handles token-based authorization and following the steps outlined above, you can create a custom role that grants access to the necessary resources.

Remember, it’s essential to practice good security habits:

  • Never expose sensitive credentials in your code or environment
  • Regularly update your Magento instance to address known vulnerabilities
  • Consider implementing IP whitelisting for your API endpoints

For more detailed guides and tips on Magento development, feel free to explore our Magento 2 Development Resources at LaravelCompany.

Happy coding!

Magento 2 Catalog Security API

Our network