/Quota/Projects URL
This URL returns a list of the names of all quota projects. To filter the projects, see
Filtering projects.
It does not return any information about the quota status of the project.
Projects and quotas are defined separately; there can be a many-to-one relationship between projects and quotas, that is, many projects can share a single quota definition. The Quota web service refers to the “project” and not the “quota project”; for example, if the “MM1WithQuota” and “MM2WithQuota” projects share the same quota definition, “MMQuota”. than accessing either MM1WithQuota or MM2WithQuota returns identical information.
XML example
<Projects>
<Project>MM1WITHQUOTA</Project>
<Project>MM2WITHQUOTA</Project>
</Projects>
JSON example
[
"MM1WITHQUOTA",
"MM2WITHQUOTA"
]
Filtering projects
To filter the list of projects, you can include query parameters. Any DPM property that is an immediate child of the project can be used as a filter. If multiple properties are specified, they are ANDed together. In addition to any filter parameters, only projects which use Quota are returned.
For example:
GET /Quota/Projects?Status=Active&GroupName=Pepsi
“Filter” query parameter
A special query parameter called “Filter” can be used to specify a filter condition that is evaluated per project by using mrEvaluate. The expression can use any of the top level project properties and a special identifier of “Name” which is the project name. The expression must to be URL encoded, for example, to search for "Name LIKE 'MyBrand_%' "
For example:
GET /Quota/Projects?Filter=%22Name%20LIKE%20%27MyBrand_%25%27%22
Any syntax error in the Filter expression is returned to the client as an error string as described in
Error handling.
See also