Get Resources

get

/resource

Gets all resources that match the search criteria specified in the query parameters.

Attribute selection is enabled for all first-level attributes.

The @type query parameter is required for optimal results.

The criteria can include these properties:

  • name
  • lifecycleState
  • lifecycleSubState
  • resourceSpecification.name
  • resourceCharacteristic.{charName} = value
  • category

These criteria operators can be used on the filtering properties. Operators can be string literals or URL-encoded format.

  • .eq (OR) = (OR) %3D%3D

    For example: lifecycleState=UNASSIGNED (OR) lifecycleState==UNASSIGNED (OR) lifecycleState%3D%3DUNASSIGNED lifecycleState.eq=UNASSIGNED

  • .gte (OR) >= (OR) %3E%3D

    For example: startDate.gte=2013-04-20 (OR) startDate>=2013-04-20 (OR) startDate %3E%3D2013-04-20

  • .lte (OR) <= (or) %3c%3d

    startDate.lte=2013-04-20 (OR) startDate<=2013-04-20 (or) startdate %3c%3d2013-04-20 < li>

  • .regex (with !)

    For example: vendorPortName.regex=!cisco (OR) vendorPortName*=!cisco

  • .regex (with ^)

    For example: vendorPortName.regex=^cisco (OR) vendorPortName*=^cisco (OR) vendorPortName*=%5Ecisco

  • .regex (with $)

    For Example: vendorPortName.regex=cisco$ (OR) vendorPortName*=cisco$ (OR) vendorPortName*=cisco%24

  • .regex (with ^.*)

    For example: vendorPortName.regex=^.*cisco (OR) vendorPortName*=^.*cisco (OR) vendorPortName*=%5E.*cisco

Optionally, use the expand parameter to specify any resource relationships (resourceRelationship.PARENT,resourceRelationship.CHILD, resourceRelationship.ASSOCIATES, resourceRelationship.INVOLVE, and resourceRelationship.MAPPEDTO) that you want to see details for. By default, you'll just see links for these.

Optionally, use the depth parameter to expand the level of referenced entities. If depth=0, all referenced entities in RootEntity objects will contain only the ID, HREF, and @type. If depth=N, it expands reference objects of related entities recursively, and the last level contains only the references. The default is depth=0.

Optionally, use the sort parameter to sort the search results.

Usage: sort=(Direction)Fields

where Direction is '-' for descending order, and '+' for ascending order. For example: sort=-id,name

These fields can be sorted:

  • id
  • name
  • description
  • lifecycleState
  • resourceSpecification.name

Request

Query Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

The resources were retrieved successfully.
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : Discriminator: @type
Type: object
A base resource Class.
Show Source
Nested Schema : externalIdentity
Type: object
Read Only: true
The external identity details for the federated resource.
Match All
Show Source
Nested Schema : place
Type: array
The list of associated geographic places.
Show Source
Nested Schema : resourceCharacteristic
Type: array
The list of characteristics for the resource.
Show Source
Nested Schema : resourceRelationship
Type: array
The list of all resources referenced with the current resource. For example, parent resource, associated resource, etc.
Show Source
Nested Schema : Specification
Type: object
A specification.
Show Source
  • Details about the specification.
  • The date and time when the specification ends.
  • Allowed Values: [ "CustomObject", "CustomNetworkAddress", "DeviceInterface", "Equipment", "EquipmentHolder", "FlowIdentifier", "GeographicLocation", "GeographicSite", "GeographicAddress", "PropertyLocation", "LogicalDevice", "LogicalDeviceAccount", "MediaStream", "Network", "PhysicalConnector", "PhysicalDevice", "PhysicalPort", "Pipe", "Service", "TelephoneNumber", "IPV4Address", "IPV6Address", "IPSubnet", "NetworkAddressDomain", "Connectivity", "Party" ]
    The list of valid values for an entity class.
  • The URI for the specification.
  • The ID of the specification, which is the same as the name of the specification.
  • The name of the specification.
  • The date and time when the specification starts.
  • The version of the specification, which is always 1.
Nested Schema : ExternalIdentity
Type: object
An external identity.
Show Source
Nested Schema : PlaceRef
Type: object
A place to associate with the resource/service.
Show Source
Nested Schema : Characteristic
Type: object
A characteristic of an object or entity represented by a name-value pair.
Show Source
Nested Schema : value
Type: object
The value of the characteristic.
Nested Schema : ResourceRelationship
Type: object
A relationship to a resource.
Show Source

206 Response

A range of resources were returned successfully.
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : Discriminator: @type
Type: object
A base resource Class.
Show Source
Nested Schema : externalIdentity
Type: object
Read Only: true
The external identity details for the federated resource.
Match All
Show Source
Nested Schema : place
Type: array
The list of associated geographic places.
Show Source
Nested Schema : resourceCharacteristic
Type: array
The list of characteristics for the resource.
Show Source
Nested Schema : resourceRelationship
Type: array
The list of all resources referenced with the current resource. For example, parent resource, associated resource, etc.
Show Source
Nested Schema : Specification
Type: object
A specification.
Show Source
  • Details about the specification.
  • The date and time when the specification ends.
  • Allowed Values: [ "CustomObject", "CustomNetworkAddress", "DeviceInterface", "Equipment", "EquipmentHolder", "FlowIdentifier", "GeographicLocation", "GeographicSite", "GeographicAddress", "PropertyLocation", "LogicalDevice", "LogicalDeviceAccount", "MediaStream", "Network", "PhysicalConnector", "PhysicalDevice", "PhysicalPort", "Pipe", "Service", "TelephoneNumber", "IPV4Address", "IPV6Address", "IPSubnet", "NetworkAddressDomain", "Connectivity", "Party" ]
    The list of valid values for an entity class.
  • The URI for the specification.
  • The ID of the specification, which is the same as the name of the specification.
  • The name of the specification.
  • The date and time when the specification starts.
  • The version of the specification, which is always 1.
Nested Schema : ExternalIdentity
Type: object
An external identity.
Show Source
Nested Schema : PlaceRef
Type: object
A place to associate with the resource/service.
Show Source
Nested Schema : Characteristic
Type: object
A characteristic of an object or entity represented by a name-value pair.
Show Source
Nested Schema : value
Type: object
The value of the characteristic.
Nested Schema : ResourceRelationship
Type: object
A relationship to a resource.
Show Source

400 Response

The request isn't valid.
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. This is typically used with HTTP error response codes (3xx, 4xx, 5xx).
Show Source
  • The error code.
  • Allowed Values: [ "CustomObject", "CustomNetworkAddress", "DeviceInterface", "Equipment", "EquipmentHolder", "FlowIdentifier", "GeographicLocation", "GeographicSite", "GeographicAddress", "PropertyLocation", "LogicalDevice", "LogicalDeviceAccount", "MediaStream", "Network", "PhysicalConnector", "PhysicalDevice", "PhysicalPort", "Pipe", "Service", "TelephoneNumber", "IPV4Address", "IPV6Address", "IPSubnet", "NetworkAddressDomain", "Connectivity", "Party" ]
    The list of valid values for an entity class.
  • message
    The text that provides more details about the error as well as corrective actions.
  • The short, user-friendly summary of the problem, which does not change for subsequent occurrences of the problem.
  • The URL pointing to the documentation that describes the error.
  • The HTTP error code extension, such as 400-2.
Nested Schema : message
Type: array
The text that provides more details about the error as well as corrective actions.
Show Source

401 Response

You aren't authorized to make this request.
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. This is typically used with HTTP error response codes (3xx, 4xx, 5xx).
Show Source
  • The error code.
  • Allowed Values: [ "CustomObject", "CustomNetworkAddress", "DeviceInterface", "Equipment", "EquipmentHolder", "FlowIdentifier", "GeographicLocation", "GeographicSite", "GeographicAddress", "PropertyLocation", "LogicalDevice", "LogicalDeviceAccount", "MediaStream", "Network", "PhysicalConnector", "PhysicalDevice", "PhysicalPort", "Pipe", "Service", "TelephoneNumber", "IPV4Address", "IPV6Address", "IPSubnet", "NetworkAddressDomain", "Connectivity", "Party" ]
    The list of valid values for an entity class.
  • message
    The text that provides more details about the error as well as corrective actions.
  • The short, user-friendly summary of the problem, which does not change for subsequent occurrences of the problem.
  • The URL pointing to the documentation that describes the error.
  • The HTTP error code extension, such as 400-2.
Nested Schema : message
Type: array
The text that provides more details about the error as well as corrective actions.
Show Source

403 Response

The request is forbidden.
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. This is typically used with HTTP error response codes (3xx, 4xx, 5xx).
Show Source
  • The error code.
  • Allowed Values: [ "CustomObject", "CustomNetworkAddress", "DeviceInterface", "Equipment", "EquipmentHolder", "FlowIdentifier", "GeographicLocation", "GeographicSite", "GeographicAddress", "PropertyLocation", "LogicalDevice", "LogicalDeviceAccount", "MediaStream", "Network", "PhysicalConnector", "PhysicalDevice", "PhysicalPort", "Pipe", "Service", "TelephoneNumber", "IPV4Address", "IPV6Address", "IPSubnet", "NetworkAddressDomain", "Connectivity", "Party" ]
    The list of valid values for an entity class.
  • message
    The text that provides more details about the error as well as corrective actions.
  • The short, user-friendly summary of the problem, which does not change for subsequent occurrences of the problem.
  • The URL pointing to the documentation that describes the error.
  • The HTTP error code extension, such as 400-2.
Nested Schema : message
Type: array
The text that provides more details about the error as well as corrective actions.
Show Source

404 Response

The resources weren't found.
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. This is typically used with HTTP error response codes (3xx, 4xx, 5xx).
Show Source
  • The error code.
  • Allowed Values: [ "CustomObject", "CustomNetworkAddress", "DeviceInterface", "Equipment", "EquipmentHolder", "FlowIdentifier", "GeographicLocation", "GeographicSite", "GeographicAddress", "PropertyLocation", "LogicalDevice", "LogicalDeviceAccount", "MediaStream", "Network", "PhysicalConnector", "PhysicalDevice", "PhysicalPort", "Pipe", "Service", "TelephoneNumber", "IPV4Address", "IPV6Address", "IPSubnet", "NetworkAddressDomain", "Connectivity", "Party" ]
    The list of valid values for an entity class.
  • message
    The text that provides more details about the error as well as corrective actions.
  • The short, user-friendly summary of the problem, which does not change for subsequent occurrences of the problem.
  • The URL pointing to the documentation that describes the error.
  • The HTTP error code extension, such as 400-2.
Nested Schema : message
Type: array
The text that provides more details about the error as well as corrective actions.
Show Source

500 Response

An internal server error occurred.
Body ()
Root Schema : Error
Type: object
Used when an API throws an error. This is typically used with HTTP error response codes (3xx, 4xx, 5xx).
Show Source
  • The error code.
  • Allowed Values: [ "CustomObject", "CustomNetworkAddress", "DeviceInterface", "Equipment", "EquipmentHolder", "FlowIdentifier", "GeographicLocation", "GeographicSite", "GeographicAddress", "PropertyLocation", "LogicalDevice", "LogicalDeviceAccount", "MediaStream", "Network", "PhysicalConnector", "PhysicalDevice", "PhysicalPort", "Pipe", "Service", "TelephoneNumber", "IPV4Address", "IPV6Address", "IPSubnet", "NetworkAddressDomain", "Connectivity", "Party" ]
    The list of valid values for an entity class.
  • message
    The text that provides more details about the error as well as corrective actions.
  • The short, user-friendly summary of the problem, which does not change for subsequent occurrences of the problem.
  • The URL pointing to the documentation that describes the error.
  • The HTTP error code extension, such as 400-2.
Nested Schema : message
Type: array
The text that provides more details about the error as well as corrective actions.
Show Source
Back to Top

Examples

This example shows how to get the details of a resource with the given discriminator "@type" by submitting a GET request on the REST resource using cURL. For more information about cURL, see "Install and Use cURL".

cURL Command

curl -X GET "http://hostname:port/InventoryRSOpenAPI/resourceInventoryManagement/version/resource?@type=discriminator&fields=none" -H credentials

where:

  • hostname is the URL for the UIM REST server.
  • port is the port for the UIM REST server.
  • version is the version of the API you're using.
  • credentials is the base64 encoding of the user ID and password joined by a single colon (ID:password). See "Authentication and Authorization".
  • discriminator is the value of the concrete resource, such as LogicalDevice, PhysicalDevice, or so on.

Example of Response Body

This example shows the contents of the response body in JSON format. It shows the list of resources for a discriminator @type of "LogicalDevice".

[
   {
      "id": "1-150001",
      "href": "http://hostname:port/InventoryRSOpenAPI/resourceInventoryManagement/version/resource/1-150001",
      "@type": "LogicalDevice"
   },
   {
      "id": "1-225001",
      "href": "http://hostname:port/InventoryRSOpenAPI/resourceInventoryManagement/version/resource/1-225001",
      "@type": "LogicalDevice"
   },
   {
      "id": "1-300001",
      "href": "http://hostname:port/InventoryRSOpenAPI/resourceInventoryManagement/version/resource/1-300001",
      "@type": "LogicalDevice"
   },
]
Back to Top