`REST` api throws `NotFound` if custom `id` contains `/` symbol about payload HOT 3 CLOSED

Thanks both! We'll make sure this is documented for v2 and v3

from payload.

I'm not sure, but it looks like it can be pretty hard to fix. It's a part of URL, so next API route is catching it as a separate routes and is looking for handlers for foo(it's an ID for API) and bar(it's a separate route inside foo).

It's kind of agains REST API rules to have any ID's for routes with / when it is not the last route.

Maybe you could try to rewrite your logic to use underscore or hyphen with a help of a conversion util.

from payload.

Thanks for your reply.
I'm not using / in id. I just find out it accidentally when create element with / in id via admin UI and then got NotFound page. So I created the issue because it's unexpected and undocumented behavior.
I agree, it's hard to fix (and unnecessary). You can close this issue.
And may be, you can add a note to the cusmozible id documentation (about some symbols in id can break some REST-api operations).

from payload.