Civic open-data clients want to request exactly the nested fields they need from a flexible API schema instead of over-fetching fixed REST resources. Which API style addresses that need?
Select an answer to reveal the explanation.
Short Explanation
Open-data apps hate dragging home whole objects when they only need two nested fields—GraphQL lets them ask for exactly that. It is a query-oriented API style built around flexible schemas. Fixed dumps and "return everything" SOAP miss that selectivity.
Full Explanation
GraphQL provides a query-oriented API model in which clients specify the nested fields required in a single request, reducing over-fetching common with fixed REST resources. Bulk file exports and SOAP operations that always return full payloads do not offer the same client-driven selection. Cloud+ expects recognition of GraphQL among modern integration styles.