Abstract: An aspect includes identifying one or more dependencies, via a feature toggle component of an application programming interface (API), with respect to features associated with a set of resources. An aspect also includes populating identified dependencies within a metadata table corresponding to the API and defining a multi-level access control feature for the resource. The multi-level access control includes a top level that identifies the resource, and a mid level that identifies a first set of properties for the resource. An aspect further includes populating fields in the metadata table with the first set of properties and a corresponding mid-level indicator, and enabling access to the resource at varying levels of granularity based on the identified dependencies in the metadata table for the resource and the mid level-indicator for the first set of properties.

Abstract: Examples are generally directed towards managing query responses. A server receives an unspecified property request associated with a resource. The request identifies a resource and omits a property field parameter. A set of instances associated with the resource is identified. An identifier for each instance in the set of instances is identified to form a set of identifiers. The server returns only the set of identifiers to the client as a response to the unspecified property request. On determining the server has received a types-feed request from the client, the server identifies all possible property types for the resource to form a list of all property types. The server returns the list of all property types to the client as a response to the types-feed request.

Abstract: Examples are generally directed towards managing paginated data. A server receives a page-to-identifier query from a client. The page-to-identifier query includes an identifier of a selected object instance. The server generates an ordered list of object instances corresponding to at least one ordering criteria paginated into a set of pages. The server identifies a page in the set of pages including the selected instance to form a results page. The results page includes the selected instance. The server returns the results page to the client.

Abstract: Described are techniques for consolidating tasks into a composite job. A server processes a composite request to create a composite job on the server. The composite request comprises a plurality of nested job create requests. The composite job comprises a plurality of jobs. Each job in the plurality of jobs corresponds to a job create request in the plurality of nested job create requests. The server generates a dependency tree indicating a dependency of each job in the plurality of jobs. The server executes the composite job in accordance with the dependency tree. On determining that a first job is dependent on a second job, the server executes the second job prior to executing the first job. The server passes the output of the second job as input to the first job.