The request header is used for authentication parsing in the underlying requests made. Path and query parameters included in the request header are ignored in favor of the data within the topLevelRequests fields.
A non-empty list of "roots" used to begin queries. Every query begins with a "base" resource and related models are joined upon it from there.
The request header is used for authentication parsing in the underlying requests made.
The request header is used for authentication parsing in the underlying requests made. Path and query parameters included in the request header are ignored in favor of the data within the topLevelRequests fields.
A non-empty list of "roots" used to begin queries.
A non-empty list of "roots" used to begin queries. Every query begins with a "base" resource and related models are joined upon it from there.
This encapsulates all of the information needed to compute a response.
The request header is used for authentication parsing in the underlying requests made. Path and query parameters included in the request header are ignored in favor of the data within the topLevelRequests fields.
A non-empty list of "roots" used to begin queries. Every query begins with a "base" resource and related models are joined upon it from there.