In case the value of an identifier property of a feature includes a '/', the routing fails
Url-encoding the value doesn't seem to improve the case (Apache decodes the URL before launching CGI, unless apache is configured to keep slashes; AllowEncodedSlashes NoDecode)
Same probably applies to special characters such as "?/&"

https://kenya.lsc-hubs.org/ows/vector/ogcapi/collections/Potato_suitability/items/KE104/2-149 vs
https://kenya.lsc-hubs.org/ows/vector/ogcapi/collections/Potato_suitability/items/KE104%2F2-149

{"code":"NotFound","description":"Invalid API path."}