GraphQL endpoint with generated API, introspection, and mutation behavior

[vardhanapoorv (Apoorv Vardhan)]

Hi @forstmeier

If you want to remove a value from list you should use remove and use the delete mutation if you want to delete like the complete customer in this case. I think when you check the generated mutations and queries definitions that will make it easy for you. So I’m attaching the screenshots from Insomnia (you could be using a different tool) to try/view queries or mutations.

I hope these will help you to view queries/mutations available to you.

Thanks for the typo mention. Btw here are the two posts I told you that were coming out soon.

GraphQL Authorisation

We are working on a new batch of GraphQL features. One of those is the ability to get your API protected by automated authorisation. There’s a first version built that we are moving through testing and into a beta release. It’ll be part of beta releases until the release of 20.07.0. We are really keen to get feedback and make this the most useful feature it can be. Docs and examples will also land pretty soon. But seeing as there’s been lots of interest in this sort of feature I’m putting up t…

GraphQL Custom Logic

We are working on a new batch of GraphQL features. One of those is the ability to extend the generated GraphQL API with custom logic. There’s a first version built that we are moving through testing and into a beta release. It’ll be part of beta releases until the release of 20.07.0. We are really keen to get feedback and make this the most useful feature it can be. Docs and examples will also land pretty soon. But seeing as there’s been lots of interest in this sort of feature I’m putting…

Let me know if you have anymore questions.