I am not sure, of that is by design, but as far as I can tell, the JSONAPI is usually very picky.
i requested something like this:
http://localhost:3000/proxy/jsonapi/profile/experience/3a713f0a-30c3-4b66-96a4-894df0f97801
and got back:
{
"jsonapi": {
"version": "1.0",
"meta": {}
},
"data": {
"type": "profile--customer",
"id": "3a713f0a-30c3-4b66-96a4-894df0f97801",
"attributes": {
"foobar1": "no",
"foobar2": "CA",
...
which means that the query/fetch command have found a profile (Profile module), with a UUID, but ignored the bundle (the /profile/experience part). Which is odd to me. If that is by design. okay, if not, it might be a bug somewhere.
I would expect an json:api error message or 404 result, that no profile of bundle type "experience" with that UUID was found.
Closed: duplicate
10.2 ✨
Last updated
Hmm, yeah this is a known issue. See #3166443: Jsonapi: Bundle is largely ignored when requesting specific resource by uuid → . There is an intial fix available there, kinda just need some tests and we could fix this.