POST Config/Find

Returns objects based on their attribute values.


  • Permissions:  The caller must have Read permission to objects in order for them to appear in the results.
  • Token scope:  Configuration


  • Content type: Content-Type:application/json.

  • Token: The bearer access token that you received. For example, Authorization:Bearer 4MyGeneratedBearerTknz==. For more information, see Passing a bearer token in your API calls.


Input parameters




A pattern to match against object attribute values:

  • To list DNs that include an asterisk (*) or question mark (?), prepend two backslashes (\\). For example, \\* treats the asterisk as a literal character and returns only certificates with DNs that match *
  • To list DNs with a wildcard character, append a question mark (?). For example, "test_?" counts and but not
  • To list DNs with similar names, prepend an asterisk. For example, *, counts and
  • You can also use both literals and wildcards in a pattern.

    NOTE  Web SDK wildcards operate differently than the UI wildcards. For REST API calls, be sure to follow the guidelines stated in this section.

AttributeNames (Optional)

A list of attribute names to limit the search against. For more information, see How to find class names and attributes.


Response description



HTTP 200

For valid requests, this call returns a HTTP 200 message and the following data in the message body:

  • Error: Appears only when the operation cannot supply the necessary data. Provides only a description and Result. No other data.
  • Objects: An array of found objects:

    • AbsoluteGUID: The left-to-right concatenation of all of the GUIDs for all of the objects in the DN.
    • DN: The Distinguished Name (DN) of the object.
    • GUID: The GUID that identifies the object.
    • ID: The object identifier.
    • Name: The Common Name (CN) of the object.
    • Parent: The parent DN of the object.
    • Revision: The revision of the object.
    • TypeName: the class name of the object.
  • Result: The result code that indicates the reason for success or failure. For more information, see Config result codes.

HTTP 400

For invalid requests, this call returns HTTP 400 Bad Request and the following data in the message body:

  • error: The reason for the error.
  • error_description: If available, additional information about how to retry the request.

Example: Use an attribute value to find an object


POST https://tpp.venafi.example/vedsdk/Config/Find
Authorization:Bearer 4MyGeneratedBearerTknz==


HTTP/1.1 200 OK