SELECT fields that I want Query Contents endpoints to return

I have…

  • Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
  • Used code blocks with ``` to format my code examples like JSON or logs properly.

I’m submitting a…

  • Regression (a behavior that stopped working in a new release)
  • Bug report
  • Performance issue
  • Documentation issue or request
  • Question about the REST Api / TypeScript SDK

Question

Hi Squidex Team,

I would like to know if there is a way to select which field I want the REST API to return in order to reduce the size of the response for the Query Contents (GET & POST) endpoints:

I think the ODATA protocol allows you to specify a list of field with the $select parameter. e.g.: {endpoint_url}?$select=id,name,slug,etc.

I know it is possible with the GraphQL API, but I would like to know if it is possible to do the same with the REST API (I use the TypeScript SDK since it looks like it manages the token by itself, which saves us time).

Environment

App Name: nexapp-alloprof-ei-pronominalisation

  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: 7.0.0.0 (dev) and 7.9.0.0 (staging)

I use the free squidex plan just for development purpose, but my client has a self hosted version on staging.

Thanks in advance for your support !

@Lucas_Catchlove will take ownership of this issue since I will be out of office for a few weeks.

Hi there,

As Nicolas mentioned, please redirect all communication my way for the time being.

Thank you!

Odata has never been fully implemented. Initially it was used for the filters because I thought it would be easier (it is not) and then whenever more advanced features have been requested I was and still be pointing towards GraphQL. Long answer short: use graphql :wink: