Title: Bug in REST API
Last modified: November 30, 2023

---

# Bug in REST API

 *  Resolved [imberdev](https://wordpress.org/support/users/imberdev/)
 * (@imberdev)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/bug-in-rest-api/)
 * Hello,
 * I’ve encountered an issue while utilizing your plugin’s REST API endpoints, specifically
   when interacting with the “**/wp-json/lmfwc/v2/licenses/{license_key}**” endpoints.
   It appears that when the `{license_key}` contains certain special characters 
   such as ‘@’, ‘/’, or others, it disrupts the API request flow, leading to an 
   unexpected error:
 *     ```wp-block-code
       {
         code: 'rest_no_route',
         message: 'No route was found matching the URL and request method.',
         data: { status: 404 }
       }
       ```
   
 * Steps to Reproduce:
    1. Use a `{license_key}` containing special characters like ‘@’, ‘/’, etc.
    2. Make a request to any of the “/wp-json/lmfwc/v2/licenses/{license_key}” endpoints
       via the REST API.
 * Expected Behavior: 
   The API should be able to process requests with `{license_key}`
   values containing special characters without encountering routing or handling
   issues.
 * Additional Notes:
    - I attempted to address this by using `encodeURIComponent()` to encode the 
      special characters within the `{license_key}` before making the request. However,
      the issue persisted.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [WPExperts.io](https://wordpress.org/support/users/wpexpertsio/)
 * (@wpexpertsio)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/bug-in-rest-api/#post-17245602)
 * Hello [@imberdev](https://wordpress.org/support/users/imberdev/)
   Thanks for reaching
   us, we are aware of this issue and we will release the fix in upcoming release.
 *  Plugin Support [Mirza Hamza](https://wordpress.org/support/users/hamza1010/)
 * (@hamza1010)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/bug-in-rest-api/#post-17256460)
 * Hello [@imberdev](https://wordpress.org/support/users/imberdev/),
 * We have recently released and updated the License Manager for WooCommerce plugin(**
   Version: 3.0.5** ).
 * Please update the plugin on your site and let me know if you still have any issues.
 * Thank you
 *  [wpsupacc](https://wordpress.org/support/users/wpsupacc/)
 * (@wpsupacc)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/bug-in-rest-api/#post-17353498)
 * Got the same problem, needed to rollback to v2 to have this resolved
 *  Plugin Support [Mirza Hamza](https://wordpress.org/support/users/hamza1010/)
 * (@hamza1010)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/bug-in-rest-api/#post-17353914)
 * Hello [@wpsupacc](https://wordpress.org/support/users/wpsupacc/),
 * We have replied to the new thread. Please follow up there.
 * Thank you

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Bug in REST API’ is closed to new replies.

 * ![](https://ps.w.org/license-manager-for-woocommerce/assets/icon-256x256.gif?
   rev=2824216)
 * [License Manager for WooCommerce](https://wordpress.org/plugins/license-manager-for-woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/license-manager-for-woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/license-manager-for-woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/license-manager-for-woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/license-manager-for-woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/license-manager-for-woocommerce/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [Mirza Hamza](https://wordpress.org/support/users/hamza1010/)
 * Last activity: [2 years, 4 months ago](https://wordpress.org/support/topic/bug-in-rest-api/#post-17353914)
 * Status: resolved