Query field collections in API

From https://www.drupal.org/api:

All requests must either have an Accept: [application/json|application/xml] request header or .[json|xml] extension.

I changed that from italic to bold, so it might be more visible now.

The https://www.drupal.org/project/restws module is designed to work alongside URLs like https://www.drupal.org/node/2429155 that return HTML. We prefixed the API URLs because we already have some modules overriding menu items, and didn't have the QA resources to test for conflicts, and #1969466: Fix GET /node/1 with page caching.

#2253947: format suffix not added to next-first-last page url's proposes adding those suffixes.

This may not be ideal, but the RestWS module is doing what it promises to do. We can upgrade to newer versions of RestWS when they are available.

https://www.drupal.org/api-d7/field_collection_item.json?field_release_f... does work for me.

Ah, I see

The "Access the resource field_collection_item" permission is granted to anonymous users, so the next step is to figure out what else RestWS is checking for access.

This is still an issue to this day. In my case I'm trying to configure a slack bot that can pull recently worked on issues for all users that have our organization listed on their accounts. The goal being to help better facilitate our internal work within Drupal community. Since the associate of organization and user is stored within a field collection ideally I would like a request similar to the following to work

https://www.drupal.org/api-d7/field_collection_item.json?field_organization_name=Mindgrub Technologies
https://www.drupal.org/api-d7/field_collection_item.json?field_organization_reference=2497975

What's interesting is that I can access individual field collections by id

https://www.drupal.org/api-d7/field_collection_item/1257183.json
https://www.drupal.org/api-d7/field_collection_item/898911.json
https://www.drupal.org/api-d7/field_collection_item/1350533.json

For reference for the above

## Organization Node
title: Mindgrub Technologies
nid: 2497975

## Sample Mindgrub Users
### user 1
name: aczietlow
id: 1616656

### user 2
name: rvtraller
id:  2229370

Regarding #9 I agree that is the next step. Is this something that I would be able to investigate. If so how would I go about that? I've never worked on d.o. infra and am not aware if the configuration is publicly available.

*polite bump* We're hoping to build some tools to better facilitate contrib work within our agency, and this is a blocker.

I'm willing to put in the time for any work that needs to be done to resolve this issue, but I could use some direction. I don't know if this issue is with the RESTWS module, or with d.o.'s implementation of access checks on the RESTWS provided endpoints.

From #3056913: Drupal.org Rest API Query for all users of an organization https://www.drupal.org/api-d7/field_collection_item.json?field_name=fiel... is another example that works while logged in with a session cookie, but not while logged out.

Thanks for the reply. I still get a 403 when trying, even with my session cookie set. I'll try looking at #2344265 It's a rabbit hole I haven't been down yet.

(updated to reformat using the issue reference instead of url)

Same holds for "replaced by" info on projects. See https://www.drupal.org/api-d7/node.json?field_project_machine_name=cck lists items like https://www.drupal.org/api-d7/field_collection_item/1399291 which are not possible to follow.

https://www.drupal.org/api-d7/field_collection_item/1399291.json does work, and adding an Accept: application/json request header would also work. See the “All requests must either have” note on https://www.drupal.org/drupalorg/docs/api. (RestWS module usually takes over the core paths, as in /node/3060.json or /node/3060 with the accept header, but we serve the API from a different root path on www.drupal.org.)

I tracked this down to https://git.drupalcode.org/project/field_collection/-/blob/1913cdf5aaec9...

RestWS is calling entity_access(), which calls field_collection_item_access('view', NULL). This looks like it is expected to return whether the user has general view access on that entity type. Instead field_collection is denying access to the item that does not exist.

I do not see any issues for this specifically yet.