Is it possible to hide/prevent a certain Collection from generating REST and GQL endpoints?

[tonyjmnz-ss]

Hi, I'm working with a Collection which I would only access via Local API, as it needs data from a third party to be meaningful.

I'm creating a custom GraphQL endpoint where I'm planning to do this aggregation, but the issue I'm facing is that I'm ending up with all the Collection-related endpoints in my GQL schema, and I wouldn't like to expose that to consumers so it's less confusing.

Is there a way to achieve this?

EDIT: I saw it's possible to hide the GQL endpoints but what about REST?

[matthijs166]

You can make all the fields hidden so that only the admin API can access the data by default.

The REST API does not have a general schema like GQL so you need to guess the endpoint.
It is possible to see the collection in the /access call, but if you have setup access control the collection won't show.

It's also possible to create a custom REST endpoint or make jobs to handle the task.