When using FeCru REST APIs, if the name of the object, such as permission scheme, contains a slash character ( / ), then the call will fail with 404, even if the slash is replaced with its URL encoded character(s).

The suggestion here is to either:

• support slash (or its URL encoded character) in the REST API
• add support for object IDs, rather than names, in the REST API
• ensure an object cannot be created with a slash in its name

The last option is based off current workaround of renaming the object without the slash in the name.