Chat now with support
Chat with Support

Quest has tools and processes in place to identify, protect, detect, and remediate vulnerabilities and incidents when they occur, including external security partners. As part of our standard security operations, Quest does not use CrowdStrike in any of our operations. We are reviewing our third parties, and so far, there is minimal affect. It is Quest's policy not to provide further technical details unless they directly impact customer data.

Identity Manager 9.1 - API Development Guide

Date formats

Date values in requests to change or add objects must be specified in ISO 8601 format in the client's local time zone.

Example

2016-03-19T13:09:08.123Z

Related topics

Parameter formats

HTTP requests use the following types of parameters:

Related topics

Path parameters

Path parameters extend the URL path. A forward slash is used as the delimiter.

If a query uses a path parameters, they are given in URI format.

Example

https://<host name>/ApiServer/imx/sessions/exampleparameter

Query parameters

Query parameter are appended to the URL with a question mark (?) or an ampersand (&).

The first query parameter must be prefixed by a question mark. In this case, you must use the following format:

?parameter name=parameter value (for example, ?orderBy=LastName)

Subsequent query parameters must be prefixed by an ampersand. In this case, you must use the following format:

&parameter name=parameter value (for example, ?sortOrder=ascending)

NOTE: Unknown query parameters are rejected by the server with error code 400. This also affects query parameters with incorrect upper and lower case spelling.

Example

https://<host name>/AppServer/portal/person?orderBy=LastName

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating