DAM category with /slash throws errors

Problem/Motivation

We have a category in our DAM called "Category with /slash" and since it has been created we see errors for requests to /acquia-dam/categories?category=Category%20with%20/slash while browsing the DAM in our site's media library that look like:

Client error: `GET
GET https://api.widencollective.com/v2/categories/Category%20with%20/slash` resulted
in a `400 Bad Request` response:
{
"error": true,
"response_code": 400,
"error_message": "Invalid category path: Category with /slash", "stack_tr (truncated...)
}

All the other categories are working fine, so I suspect the handling of the slash in the category name is the culprit. Quoting Widen API documentation:

“Slashes in category names must be escaped with a preceeding backslash (%2F).”