A visual language for querying and updating graphs
The filter is a predicate applied to all outgoing edges of the actor.
Access the full capabilities of your data from a single endpoint.You provide functions for each field in the type system, and Graph QL calls them with optimal concurrency.Developers were able to experiment with the preview GQL and Share Point Online Search REST APIs for querying the Office Graph for quite some time now.Apps using Graph QL are fast and stable because they control the data they get, not the server.Graph QL queries access not just the properties of one resource but also smoothly follow references between them.Aging fields can be deprecated and hidden from tools.
By using a single evolving version, Graph QL APIs give apps continuous access to new features and encourage cleaner, more maintainable server code.
While typical REST APIs require loading from multiple URLs, Graph QL APIs get all the data your app needs in a single request.
Apps using Graph QL can be quick even on slow mobile network connections.
You can use these to do a combined search on the contents of a whole item and the interactions people have had with this particular item. If you want to match all items without filtering any part of the content, you can use an asterisk (*). The ACTOR operator finds all actions of the given actor that satisfies a filter and then returns all the objects for these actions.
For example, to return documents modified by Carl Steadman (assuming the Actor Id = 1234 for Carl Steadman) you can split this information into: The Actor Id is the ID of the node you want to look up the actions for.
The Insights APIs, together with other APIs exposed in Microsoft Graph, such as the People API, should be used as a replacement.