Resources are identified by URIs.
Resources are identified by URIs, and can be either:
A strict set of request methods are allowed for a resource type. Resources support the JSON representation type.
Tip: For a comprehensive list of supported public resources and their details, see the description of the Interactive API client.
You do not need to send any additional headers (other than the content-type header) when sending REST API requests for public resources.
For documentation on the generic and CI/CD resources, see the Interactive API client.
Public, supported resources include:
Note: The product_area resource is also known as an application_module.
Resources not listed above as public are subject to change until declared public. To access these resources, send REST API requests with a header:
Resources are built as a hierarchy of collections and instances.
Some resources are singleton resources, such as: test-results, sign_in, and sign_out.
The following example represents a resource collection of humans. This collection contains resource instances of human. Since humans have limbs, every human contains a collection of limbs. This collection contains resource instances of limb. Since limbs have fingers, every limb contains a collection of fingers. This collection contains resource instances of finger.
humans human limbs limb fingers finger finger limb fingers finger finger human limbs ...
Since resources represent entities, resource names should represent the entities' names (for example, defect).
Resource instances should be called by their names in singular (for example, defect).
Resource collections should be called by their names in plural (for example, defects).
A resource whose name is more than one word is separated by the underscore symbol (for example, ci_servers).