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:

{
  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.