200

successful operation

{
  running: boolean*
  Are there any discovery runs in progress?
 
  status: string*
  Current status of the discovery process
  Enum: [
    "starting",
    "running",
    "stopping",
    "stopped"
  ]
}

body

body

{
  status: string*
  Desired status of the discovery
  Enum: [
    "running",
    "stopped"
  ]
 
  passphrase: string
  Passphrase to open the vault before starting discovery. Only required if the vault is closed and protected by a passphrase.
}

200

successful operation

200

successful operation

[
  A list of cloud providers, along with information on the fields required to create cloud scans and cloud credentials for each provider
 
   {
    provider: string*
    Name of the cloud provider. Used for the 'scan_params.provider' field in the /discovery/runs endpoints, and as an entry in the 'types' list in the /vault/credentials endpoints
 
    scan_params: [
      List of additional 'scan_params' fields this cloud provider supports in the /discovery/runs endpoint
 
       {
        name: string*
        Name of the field in the 'scan_params' object
 
        description: string*
        type: string*
        The type of this field
 
        is_list: boolean*
        Whether this field is a list of values or a single instance
 
        mandatory: boolean*
        Whether this field is required to create a new cloud scan or can be skipped
 
        allowed_values: {
          The allowed values for this field. The values are the keys of this object, with descriptions for the values
        }*
      }
    ]*
 
    cred_params: [
      List of additional fields this cloud provider supports in the /vault/credentials endpoints
 
       {
        name: string*
        Name of this field in the credentials object
 
        description: string*
        type: string*
        The type of this field
 
        is_list: boolean*
        Whether this field is a list of values or a single instance
 
        mandatory: boolean*
        Whether this field is required to create a new cloud credential or can be skipped
 
        allowed_values: [
          The allowed values for this field
 
          string
        ]*
      }
    ]*
  }
]

200

successful operation

[
   run {
    cancelled: string
    If present indicates the discovery run was cancelled. Field contents provides more details.
 
    blocked: boolean
    Flag to indicate if the discovery run is blocked waiting for other prerequisites
 
    done: int64
    Number of completed addresses
 
    key: string*
    Unique identity string for the discovery run
 
    label: string*
    Label of the discovery run
 
    scan_kind: string
    If this is a Cloud scan, the 'scan_params' field will also be populated
    Enum: [
      "IP",
      "Cloud"
    ]

    outpost_id: string
    Used for IP scans only. Discovery Outpost to use for scanning range. No value means any.
 
    range_prefix: string
    Distinguish overlapping address spaces
 
    scan_level: string*
    Scan level
 
    scan_params: {
      Used for Cloud scans only. The 'provider' field contains the name of the cloud provider being scanned. Each provider also supports a different set of additional fields. Look up the cloud provider with the /discovery/cloud_metadata endpoint to see which fields to expect here
 
      provider: string*
      Name of the cloud provider being scanned
    }
 
    scan_options: scanOptions {
      Options controlling the scan. May be extended in future releases.
 
      NO_PING: boolean
      Skip ping before scanning. Used for IP scans only. If this attribute is omitted, the system default controls whether to ping or not.
    }
 
    scan_type: string*
    Type of scan
 
    scanning: int64
    Number of addresses being scanned
 
    pre_scanning: int64
    Number of addresses being pre-scanned
 
    starttime: datetime*
    Date and time the run started
 
    total: int64
    Number of addresses in the discovery run
 
    user: string*
    User who created the discovery run
 
    valid_ranges: string
    Valid IP address ranges in the run
 
    waiting: int64
    Number of addresses waiting for end of exclude range
 
    uuid: string*
    ID of the discovery run
 
    uri: string*
    URI to the detail information of the discovery run
 
    finished: boolean*
    Flag to indicate if the discovery run is finished
 
    inferred: string*
    URI to the inferred information of the discovery run
 
    results: string*
    URI to the summarized information of the discovery run
 
    consolidating: boolean*
    Flag to indicate if the discovery run is consolidated from another appliance
 
    consolidation_source: string
    Consolidating appliance name of the discovery run. If the consolidating appliance is in a cluster, this field will represent the cluster name (only present if the run is consolidated from another)
  }
]

body

body

Snapshot discovery run to be created

newRun {
  scan_kind: string
  Depending on the kind of scan chosen here, populate either the 'ranges' or 'scan_params' fields.
  Enum: [
    "IP",
    "Cloud"
  ]

 outpost_id: string
    Used for IP scans only. Discovery Outpost to use for scanning range. No value means any, 'Local discovery' means local discovery on the appliance or cluster.   

  range_prefix: string
  ranges: [
    Used for IP scans only. A list of IP addresses or ranges.
 
    string
  ]
 
  label: string*
  scan_level: string
  Enum: [
    "Full Discovery",
    "Sweep Scan"
  ]
  company: string
  scan_params: {
    Used for Cloud scans only. Populate the 'provider' field with the name of the cloud provider to scan. Each provider then requires a different set of additional fields. Look up your chosen cloud provider with the /discovery/cloud_metadata endpoint to see which fields to populate in this object.
 
    provider: string*
    Name of the cloud provider to scan
  }
 
  scan_options: scanOptions {
    Options controlling the scan. May be extended in future releases.
 
    NO_PING: boolean
    Skip ping before scanning. Used for IP scans only. If this attribute is omitted, the system default controls whether to ping or not.
  }
}

200

successful operation

{
  uuid: string*
  uri: string*
}

run_id

path

ID of the discovery run

string*

200

successful operation

run {
  cancelled: string
  If present indicates the discovery run was cancelled. Field contents provides more details.
 
  blocked: boolean
  Flag to indicate if the discovery run is blocked waiting for other prerequisites
 
  done: int64
  Number of completed addresses
 
  key: string*
  Unique identity string for the discovery run
 
  label: string*
  Label of the discovery run
 
  scan_kind: string
  If this is a Cloud scan, the 'scan_params' field will also be populated
  Enum: [
    "IP",
    "Cloud"
  ]
 
  range_prefix: string
  Distinguish overlapping address spaces
 
  scan_level: string*
  Scan level
 
  scan_params: {
    Used for Cloud scans only. The 'provider' field contains the name of the cloud provider being scanned. Each provider also supports a different set of additional fields. Look up the cloud provider with the /discovery/cloud_metadata endpoint to see which fields to expect here
 
    provider: string*
    Name of the cloud provider being scanned
  }
 
  scan_options: scanOptions {
    Options controlling the scan. May be extended in future releases.
 
    NO_PING: boolean
    Skip ping before scanning. Used for IP scans only. If this attribute is omitted, the system default controls whether to ping or not.
  }
 
  scan_type: string*
  Type of scan
 
  scanning: int64
  Number of addresses being scanned
 
  pre_scanning: int64
  Number of addresses being pre-scanned
 
  starttime: datetime*
  Date and time the run started
 
  total: int64
  Number of addresses in the discovery run
 
  user: string*
  User who created the discovery run
 
  valid_ranges: string
  Valid IP address ranges in the run
 
  waiting: int64
  Number of addresses waiting for end of exclude range
 
  uuid: string*
  ID of the discovery run
 
  uri: string*
  URI to the detail information of the discovery run
 
  finished: boolean*
  Flag to indicate if the discovery run is finished
 
  inferred: string*
  URI to the inferred information of the discovery run
 
  results: string*
  URI to the summarized information of the discovery run
 
  consolidating: boolean*
  Flag to indicate if the discovery run is consolidated from another appliance
 
  consolidation_source: string
  Consolidating appliance name of the discovery run. If the consolidating appliance is in a cluster, this field will represent the cluster name (only present if the run is consolidated from another)
}

404

Invalid run id

run_id

path

ID of the discovery run

string*

body

body

patchRunCancelled {
  cancelled: boolean*
  Flag if the discovery run should be cancelled
}

200

successful operation

boolean
Indicate if the cancellation is successfully performed

run_id

path

ID of the discovery run

string*

200

successful operation

runResultsSummary {
  Success: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  Skipped: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  NoAccess: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  NoResponse: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  Error: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  Dropped: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
}

run_id

path

ID of the discovery run

string*

result_type

path

string*
Enum: [
  "Success",
  "Skipped",
  "NoAccess",
  "NoResponse",
  "Error",
  "Dropped"
]

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

200

Returns results in the same paginated format as the search endpoints

[
   searchResults {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. A list of rows, where each cell is of any type
 
       [
        One row of results
 
         {
          A single cell in a results row. Can be of any type
        }
      ]
    ]*
 
    headings: [
      The headings for the rows in 'results'
 
      string
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

run_id

path

ID of the discovery run

string*

result_type

path

string*
Enum: [
  "Success",
  "Skipped",
  "NoAccess",
  "NoResponse",
  "Error",
  "Dropped"
]

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

200

Returns results in the same paginated format as the search endpoints

[
   searchResultsAsObjects {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. List of items represented as objects, with attribute names and values. Values can be any type.
 
       {
      }
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

run_id

path

ID of the discovery run

string*

200

successful operation

runInferredSummary {
  Host: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  MFPart: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  NetworkDevice: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  Printer: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  SNMPManagedDevice: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  ManagementController: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  StorageDevice: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  StorageSystem: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  VirtualMachine: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  LoadBalancerService: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  SoftwareInstance: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
  StorageVolume: resultsSummary {
    count: int64*
    uri: string*
    Where to go for more information
  }
}

run_id

path

ID of the discovery run

string*

inferred_kind

path

string*

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

200

Returns results in the same paginated format as the search endpoints

[
   searchResults {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. A list of rows, where each cell is of any type
 
       [
        One row of results
 
         {
          A single cell in a results row. Can be of any type
        }
      ]
    ]*
 
    headings: [
      The headings for the rows in 'results'
 
      string
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

404

No such run id or inferred kind

run_id

path

ID of the discovery run

string*

inferred_kind

path

string*

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

200

Returns results in the same paginated format as the search endpoints

[
   searchResultsAsObjects {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. List of items represented as objects, with attribute names and values. Values can be any type.
 
       {
      }
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

404

No such run id or inferred kind

query

query

string*

offset

query

The offset of the first item to return in this page of results.
 Can only be supplied if requesting results from an existing results set (by supplying a results_id).
 If you want to retrieve all items in order, this field should usually take the value of the 'next_offset' from the previous page of results.

0

integer

limit

query

Limits how many items to return in this page of results. Further items can be retrieved by making another request with a different offset.
 Use 0 to request the maximum allowed limit.
 Can vary from page to page.

100

integer

results_id

query

An opaque id that can be used to access a result set that has already been generated via a previous search request. Must be supplied if requesting an offset greater than 0.
 Note that even if retrieving results from an existing results set, the original query must be supplied in case the result set has timed out and the query needs to be re-run.
 The results_id can be found in any page of results apart from the last one.

string

delete

query

Controls whether the result set is deleted or not before results are returned.
 Result sets are deleted automatically before the last page of results are returned, but setting this field to true on any page will delete the result set immediately.
 This is an optimization to free resources if you don't plan on accessing any further pages of data. Alternatively, if set to false, automatic deletion of the result set will not happen (for this request).

boolean

200

As a search query may return multiple results sets of different kinds, the response is a list of results objects - one per kind

[
   searchResults {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. A list of rows, where each cell is of any type
 
       [
        One row of results
 
         {
          A single cell in a results row. Can be of any type
        }
      ]
    ]*
 
    headings: [
      The headings for the rows in 'results'
 
      string
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

body

body

searchQuery {
  query: string*
  The search query to run
}

200

See notes on GET endpoint results

[
   searchResults {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. A list of rows, where each cell is of any type
 
       [
        One row of results
 
         {
          A single cell in a results row. Can be of any type
        }
      ]
    ]*
 
    headings: [
      The headings for the rows in 'results'
 
      string
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

query

query

string*

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

200

As a search query may return multiple results sets of different kinds, the response is a list of results objects - one per kind

[
   searchResultsAsObjects {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. List of items represented as objects, with attribute names and values. Values can be any type.
 
       {
      }
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

body

body

searchQuery {
  query: string*
  The search query to run
}

200

See notes on GET endpoint results

[
   searchResultsAsObjects {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. List of items represented as objects, with attribute names and values. Values can be any type.
 
       {
      }
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

node_id

path

ID of node to find

string*

200

successful operation

nodeResults {
  destroyed: boolean*
  Whether the node is destroyed or not
 
  kind: string*
  The kind of the node
 
  modified: datetime*
  The last modified time of the node
 
  state: {
    The full state of the node, containing all attribute names and values
  }*
}

node_id

path

ID of node to find

string*

200

successful operation

nodeResultsRels {
  destroyed: boolean*
  Whether the node is destroyed or not
 
  kind: string*
  The kind of the node
 
  modified: datetime*
  The last modified time of the node
 
  state: {
    The full state of the node, containing all attribute names and values
  }*
 
  relationships: [
    A list of current live traversal specs that can be followed from this node.
 
    string
  ]*
}

node_id

path

ID of node to find

string*

traverse_spec

path

A traversal spec to follow and retrieve related node IDs. May be wildcarded

string*

flags

query

Search flags to use when traversing to related nodes, comma separated

[
  string
  Enum: [
    "include_destroyed",
    "exclude_current"
  ]
]

200

successful operation

nodeResultsTraverse {
  destroyed: boolean*
  Whether the node is destroyed or not
 
  kind: string*
  The kind of the node
 
  modified: datetime*
  The last modified time of the node
 
  state: {
    The full state of the node, containing all attribute names and values
  }*
 
  relationships: {
    Results of following the traversal spec, which may have been wildcarded. Maps each concrete traversal spec to a list of (relationship, target node) pairs that can be reached.
 
    default: [
       traversal {
        rel: string*
        The ID of the relationship node in this traversal.
 
        node: string*
        The ID of the target node reached in this traversal.
      }
    ]
  }*
}

node_id

path

ID of node for which the graph data is generated

string*

focus

query

Context used for determining how the graph should be traversed. Must be one of:

• 'software-connected': focuses on software and communication between items of software.
• 'software': focuses on software and communication between items of software that are in the same host.
• 'infrastructure': focuses on the connectivity to network and storage components.
   Applicable only to node kinds that are not ModelDefinition.

"software-connected"

string
Enum: [
  "software-connected",
  "software",
  "infrastructure"
]

apply_rules

query

Whether to apply global rules - which is a set of pre-defined constraints to prevent traversing to too many nodes - while obtaining the graph data.
 Applicable only to node kinds that are not ModelDefinition.

true

boolean

200

successful operation

nodeGraphResults {
  nodes: [
    List of node data involved in the graph data
 
     {
      id: string*
      ID of the node
 
      kind: string*
      Kind of the node
 
      name: string*
      Name of the node
 
      short_name: string*
      Shortened name of the node
    }
  ]*
 
  links: [
    List of relationships involved in the graph data
 
     {
      rel_id: string*
      ID of the relationship
 
      kind: string*
      Kind of the relationship
 
      src_id: string*
      ID of the source node
 
      tgt_id: string*
      ID of the target node
    }
  ]*
}

kind

path

Node kind to retrieve results for

string*

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

200

Returns results in the same paginated format as the search endpoints

[
   searchResults {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. A list of rows, where each cell is of any type
 
       [
        One row of results
 
         {
          A single cell in a results row. Can be of any type
        }
      ]
    ]*
 
    headings: [
      The headings for the rows in 'results'
 
      string
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

kind

path

Node kind to retrieve results for

string*

offset

query

0

integer

limit

query

100

integer

results_id

query

string

delete

query

boolean

200

Returns results in the same paginated format as the search endpoints

[
   searchResultsAsObjects {
    kind: string*
    The node kind of these results
 
    count: integer*
    Total number of items of this kind in the result set. Note that if your search query uses the EXPLODE keyword, there may be more rows of results returned in total than the count indicates. This is because items are exploded on demand. Therefore it is important to use the 'next_offset' when requesting the next page of results.
 
    offset: integer*
    The offset of the first item in this page of results
 
    results: [
      One page of results. List of items represented as objects, with attribute names and values. Values can be any type.
 
       {
      }
    ]*
 
    results_id: string
    The opaque id of the results set holding all results of the original search query. Must be passed back when requesting subsequent pages. Only present if there are more pages of results to be shown.
 
    next_offset: integer
    The offset to use when requesting the next page of results. Only present if there IS a next page.Note that if your search query uses the EXPLODE keyword, the 'next_offset' is the only way to know which item to request next (comparing the 'results' size and 'offset' value on this page is not guaranteed to work).
 
    next: string
    The path to the next page of results (if there IS a next page).
  }
]

200

successful operation

vault {
  open: boolean*
  passphrase_set: boolean*
  passphrase_saved: boolean*
}

body

body

patchVault {
  open: boolean*
  passphrase: string
}

200

successful operation

group

query

Filter credential types by group

string

category

query

Filter credential types by category

string

200

successful operation

[
   credentialType {
    name: string*
    label: string*
    description: string*
    groups: [
      string
    ]*
    categories: [
      string
    ]*
    uri: string*
  }
]

cred_type_name

path

Name of the credential type

string*

200

successful operation

credentialType {
  name: string*
  label: string*
  description: string*
  groups: [
    string
  ]*
  categories: [
    string
  ]*
  uri: string*
}

200

successful operation

[
   credential {
    A credential can be used for one or more types of access, with the 'types' field listing all the access types a credential applies to. See the /vault/credential_types endpoint for a list of types. The access types determine which fields from this object will be populated. Also, credentials used to access cloud providers may contain additional fields to those listed here. Look up your chosen cloud provider with the /discovery/cloud_metadata endpoint to see a list of fields.
 
    index: int64
    enabled: boolean
    username: string
    password: string
    password.cyberark: string
    label: string
    description: string
    ip_range: string
    ip_exclusion: string
    range_prefixes: [
      string
    ]
    types: [
      string
    ]*
    internal.valid: boolean
    internal.secondary: boolean
    internal.created: datetime
    internal.modified: datetime
    internal.messages: [
      string
    ]
    dip.required: [
      string
    ]
    dip.ip.name: string
    dip.ip.dynamic: boolean
    dip.fields: [
      string
    ]
    dip.match.endpoint: string
    dip.provider.type: string
    su.enabled: boolean
    su.username: string
    su.password: string
    su.password.cyberark: string
    shell.record: boolean
    shell.prompt: string
    shell.force_subshell: boolean
    vsphere.port: int64
    vsphere.timeout: int64
    vcenter.port: int64
    vcenter.timeout: int64
    windows.port: int64
    telnet.port: int64
    telnet.timeout: int64
    rlogin.port: int64
    rlogin.timeout: int64
    cimc.port: int64
    cimc.timeout: int64
    ribcl.port: int64
    ribcl.timeout: int64
    vplex.port: int64
    vplex.timeout: int64
    ssh.port: int64
    ssh.timeout: int64
    ssh.prefauth: [
      string
    ]
    ssh.key.set: boolean
    ssh.key.passphrase: string
    ssh.key.data: string
    ssh.key.passphrase.cyberark: string
    ssh.key.data.cyberark: string
    snmp.port: int64
    snmp.timeout: int64
    snmp.version: string
    snmp.retries: int64
    snmp.getbulk: boolean
    snmp.community: string
    snmp.community.cyberark: string
    snmp.v3.privkey: string
    snmp.v3.authkey: string
    snmp.v3.privkey.cyberark: string
    snmp.v3.authkey.cyberark: string
    snmp.v3.privproto: string
    snmp.v3.securityname: string
    snmp.v3.context: string
    snmp.v3.authproto: string
    wbem.http.port: int64
    wbem.https.port: int64
    wbem.http.enabled: boolean
    wbem.https.enabled: boolean
    wbem.timeout: int64
    mainview.port: int64
    mainview.timeout: int64
    export.port: int64
    export.protocol: string
    export.path: string
    uuid: string
    uri: string
    web_basic.timeout: int64
    web_basic.http.enabled: boolean
    web_digest.timeout: int64
    web_digest.http.enabled: boolean
    web_oauth2.timeout: int64
    web_oauth2.token_endpoint: string
    web_oauth2.http.enabled: boolean
  }
]

body

body

Credential to be added. Note that a default label is generated if no label is provided.

credentialInput {
  A credential can be used for one or more types of access, with the 'types' field listing all the access types a credential applies to. See the /vault/credential_types endpoint for a list of types. Different access types require different fields from this object to be populated when creating or updating a credential. Also, credentials used to access cloud providers may require additional fields to those listed here. Look up your chosen cloud provider with the /discovery/cloud_metadata endpoint to see a list of fields.
 
  index: int64
  enabled: boolean
  username: string
  password: string
  password.cyberark: string
  label: string
  description: string
  ip_range: string
  ip_exclusion: string
  range_prefixes: [
    string
  ]
  types: [
    string
  ]
  dip.required: [
    string
  ]
  dip.ip.name: string
  dip.ip.dynamic: boolean
  dip.fields: [
    string
  ]
  dip.match.endpoint: string
  dip.provider.type: string
  su.enabled: boolean
  su.username: string
  su.password: string
  su.password.cyberark: string
  shell.record: boolean
  shell.prompt: string
  shell.force_subshell: boolean
  vsphere.port: int64
  vsphere.timeout: int64
  vcenter.port: int64
  vcenter.timeout: int64
  windows.port: int64
  telnet.port: int64
  telnet.timeout: int64
  rlogin.port: int64
  rlogin.timeout: int64
  cimc.port: int64
  cimc.timeout: int64
  ribcl.port: int64
  ribcl.timeout: int64
  vplex.port: int64
  vplex.timeout: int64
  ssh.port: int64
  ssh.timeout: int64
  ssh.prefauth: [
    string
  ]
  ssh.key.set: boolean
  ssh.key.passphrase: string
  ssh.key.data: string
  ssh.key.passphrase.cyberark: string
  ssh.key.data.cyberark: string
  snmp.port: int64
  snmp.timeout: int64
  snmp.version: string
  snmp.retries: int64
  snmp.getbulk: boolean
  snmp.community: string
  snmp.community.cyberark: string
  snmp.v3.privkey: string
  snmp.v3.authkey: string
  snmp.v3.privkey.cyberark: string
  snmp.v3.authkey.cyberark: string
  snmp.v3.privproto: string
  snmp.v3.securityname: string
  snmp.v3.context: string
  snmp.v3.authproto: string
  wbem.http.port: int64
  wbem.https.port: int64
  wbem.http.enabled: boolean
  wbem.https.enabled: boolean
  wbem.timeout: int64
  mainview.port: int64
  mainview.timeout: int64
  export.port: int64
  export.protocol: string
  export.path: string
  web_basic.timeout: int64
  web_basic.http.enabled: boolean
  web_digest.timeout: int64
  web_digest.http.enabled: boolean
  web_oauth2.timeout: int64
  web_oauth2.token_endpoint: string
  web_oauth2.http.enabled: boolean
}

200

successful operation

{
  uuid: string*
  uri: string*
}

cred_id

path

ID of the credential

string*

200

successful operation

credential {
  A credential can be used for one or more types of access, with the 'types' field listing all the access types a credential applies to. See the /vault/credential_types endpoint for a list of types. The access types determine which fields from this object will be populated. Also, credentials used to access cloud providers may contain additional fields to those listed here. Look up your chosen cloud provider with the /discovery/cloud_metadata endpoint to see a list of fields.
 
  index: int64
  enabled: boolean
  username: string
  password: string
  password.cyberark: string
  label: string
  description: string
  ip_range: string
  ip_exclusion: string
  range_prefixes: [
    string
  ]
  types: [
    string
  ]*
  internal.valid: boolean
  internal.secondary: boolean
  internal.created: datetime
  internal.modified: datetime
  internal.messages: [
    string
  ]
  dip.required: [
    string
  ]
  dip.ip.name: string
  dip.ip.dynamic: boolean
  dip.fields: [
    string
  ]
  dip.match.endpoint: string
  dip.provider.type: string
  su.enabled: boolean
  su.username: string
  su.password: string
  su.password.cyberark: string
  shell.record: boolean
  shell.prompt: string
  shell.force_subshell: boolean
  vsphere.port: int64
  vsphere.timeout: int64
  vcenter.port: int64
  vcenter.timeout: int64
  windows.port: int64
  telnet.port: int64
  telnet.timeout: int64
  rlogin.port: int64
  rlogin.timeout: int64
  cimc.port: int64
  cimc.timeout: int64
  ribcl.port: int64
  ribcl.timeout: int64
  vplex.port: int64
  vplex.timeout: int64
  ssh.port: int64
  ssh.timeout: int64
  ssh.prefauth: [
    string
  ]
  ssh.key.set: boolean
  ssh.key.passphrase: string
  ssh.key.data: string
  ssh.key.passphrase.cyberark: string
  ssh.key.data.cyberark: string
  snmp.port: int64
  snmp.timeout: int64
  snmp.version: string
  snmp.retries: int64
  snmp.getbulk: boolean
  snmp.community: string
  snmp.community.cyberark: string
  snmp.v3.privkey: string
  snmp.v3.authkey: string
  snmp.v3.privkey.cyberark: string
  snmp.v3.authkey.cyberark: string
  snmp.v3.privproto: string
  snmp.v3.securityname: string
  snmp.v3.context: string
  snmp.v3.authproto: string
  wbem.http.port: int64
  wbem.https.port: int64
  wbem.http.enabled: boolean
  wbem.https.enabled: boolean
  wbem.timeout: int64
  mainview.port: int64
  mainview.timeout: int64
  export.port: int64
  export.protocol: string
  export.path: string
  uuid: string
  uri: string
  web_basic.timeout: int64
  web_basic.http.enabled: boolean
  web_digest.timeout: int64
  web_digest.http.enabled: boolean
  web_oauth2.timeout: int64
  web_oauth2.token_endpoint: string
  web_oauth2.http.enabled: boolean
}