Retrieve metric instances - Precisely Data Integrity Suite

Data Integrity Suite APIs
Product
Data_Integrity
Spatial_Analytics
Data_Enrichment
geo_addressing_1
Services
Spatial Analytics
Data Enrichment
Geo Addressing
ft:title
Data Integrity Suite APIs
ft:locale
en-US
PublicationType
pt_developer
copyrightfirst
2023
copyrightlast
2026

Get existing metric instances.

HTTP

GET https://hostname/v2/catalog/metric-instances

This API endpoint retrieves existing metric instances, allowing for flexible querying and pagination.

Request

Query parameters

Key Required Type Description
filter Yes string

Filter the results by specifying one or more filters.

field:operator(value):index

Filter operators:

  • eq Equal to
  • ne Not equal to
  • lt Less than
  • le Less than or equal to
  • gt Greater than
  • ge Greater than or equal to
  • in In a list of comma separated values
  • ni Not in a list of comma separated values
  • ct Contains a value
  • sw Starts with a value
  • ew Ends with a value
  • ex Exists (only accepts Boolean (true or false) values)

By default, multiple filter expressions are combined in an AND expression. Filter expressions can be grouped by appending the optional group index (:0, :1,…,, :n ) to each filter expression. Filters in the same group are combined using AND while different groups are combined using OR.

For example, these filter expressions are in two different groups (0 and 1), so the combined expressions return results where name is either Bob or Alice.

filter=name:eq(Bob):0&filter=name:eq(Alice):1

Filter expressions are case insensitive by default.

sort No string

Sort the results by a field in ascending or descending order.

asc(field)

or

desc(field)

Specify asc to sort in ascending order (0–9, a–z) or desc to sort in descending order (z–a, 9–0). Specify multiple sort fields with multiple sort parameters. Sorting is applied in the same order that sort query parameters are ordered.

Example: To first sort by field1 in ascending order and then by field2 in descending order, use two sort expressions:
sort=asc(field1)&sort=desc(field2)
offset No number

The number of records to skip before returning results. The minimum is 0. The default is none (0).
limit No number

The number of records to return per page. The minimum is 1.
includeTotal No boolean

Return a count of the total number of records that match the specified filter expression regardless of the number of number of records returned in the response page.

  • True — Return the total count of records that match the specified filter.
  • False — Do not return the count (default).

The count is returned by the total property in the response body. If the totalOverflow property is set to true in the response body, then the total count is an estimate that may exceed the actual number of records returned by the search.
search No boolean

Use search engine to perform the filter operation.

  • True — Use the search engine.
  • False — Do not use the search engine (default).

The search engine:

  • Performs a case insensitive search.
  • May improve performance for complex filter expressions, such as those that use the contains operator.
  • When search and includeTotal are both set to true, the search engine will always return the total number of records that match the specified filter expression.
When search is not set to true, the total count may be limited to 10,000 results with totalOverflow in the result body set to true to indicate that the total count is an estimate and may exceed the returned total.
Note: In rare cases, the search=true parameter setting may not return recently created or updated records.

Response

The successful response returns the collection of metric instances that match the filter criteria.

Response body

Example status code responses for this method are shown here. To view the response schemas, you can download the Data Catalog APIs Open API Specification from the Precisely Developer Portal..

Examples
{
  "data": [
    {
      "id": "F73e4c71389Cd45b5f1c0cfD",
      "assetId": "f2BAECdcDa1C513adCBedD8E",
      "effectiveDate": "2025-08-12T09:53:16.968Z",
      "value": "1.0",
      "correlationId": "bb62b735-b8c7-4172-b229-b2445603c838",
      "tags": [
        "QDoy4K9FnNQV02iZgubO9cYjHoh3c_ChnuQm5dz:poiYR0bw39h1L:L3S_I91jRVS3poaXz5CtT:TpSd"
      ],
      "metricTypeId": "ae086abEE8a19DBEdcF8eFAa",
      "metricGroupId": "2966A89D9e6cEF598a884d2C",
      "ruleId": "a09C3BAbE35Fe58515da1fdD",
      "parentAssetId": "54eF5540254df4fDEd08AcCc"
    }
  ],
  "links": {
    "self": "https://api.cloud.precisely.com/metric-instances"
  }
}
{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Bad Request"
}
{
  "statusCode": 401,
  "error": "Unauthorized",
  "message": "Authentication required"
}
{
  "statusCode": 404,
  "error": "Not Found",
  "message": "Resource not found"
}
{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Rate limit exceeded"
}
{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "An unexpected error occurred"
}
{
  "statusCode": 503,
  "error": "Service Unavailable",
  "message": "Service temporarily unavailable"
}
{
  "statusCode": 504,
  "error": "Gateway Timeout",
  "message": "Request timeout"
}