Resources

Resources are identified by URIs.

Overview

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.

Back to top

Supported, public resources

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.

For the most up-to-date list of ALM Octane REST API resources, see knowledge base article KM02734122.

Public, supported resources include:

Metadata resources

CI/CD resources

  • builds

  • ci_servers

  • pipelines

Generic resources

  • epics

  • features

  • stories

  • defects

  • phases

  • metaphases (GET only) 

  • transitions

  • tasks

  • releases

  • requirements

  • requirement_documents

  • requirement_folders

  • requirement_roots

  • sprints

  • product_areas
    (also known as application modules)

  • manual_tests

  • gherkin_tests

  • teams

  • team_sprints

  • tests

  • test_suites

  • test_suite_link_to_tests

  • manual_runs

  • suite_run

  • run_steps

  • runs

  • automated_runs
  • list_nodes

  • users

  • user_items

  • work_items

  • work_item_roots

  • roles

  • workspaces

  • workspace_roles

  • workspace_users

  • user_tags (GET and POST)
  • taxonomy_category_nodes

  • taxonomy_item_nodes

  • taxonomy_nodes

  • attachments

  • comments

Custom resources

Back to top

Technical preview resources

Resources not listed above as public are subject to change until declared public. To access these resources, send REST API requests with a header:

Header:  HPECLIENTTYPE

Value: ALM_OCTANE_TECH_PREVIEW

Back to top

Resource hierarchy

Resources are built as a hierarchy of collections and instances.

Some resources are singleton resources, such as: test-results, sign_in, and sign_out.

Example: Start with 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
...

Back to top

Resource naming conventions

  • 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).

Back to top

See also: