Identity Manager 9.2 - REST API Reference Guide

Create a single entity Create a batch of single entities Get a single entity Change a single entity Change a batch of single entities Delete a single entity Delete a batch of single entities Call a method on an entity Generate an event for an entity

Assignments

Get assignments for a specific entity Add assignments Remove assignments

Scripts

Run script request

Windows PowerShell sample

Query parameters

Guidelines and conventions > Parameter formats > Query parameters

Query parameters are included in the URI path using a question mark or ampersand. For example, to receive a list of identities ordered by their surname, after specifying the table Person as a path parameter, you specify an orderBy as a query parameter. The following shows the URI format for this request:

<BaseURL>/api/entities/{table}

Example:

https://<Hostname>/AppServer/api/entities/person?orderBy=LastName

The first query parameter is preceded by a question mark, using the following format:

?parameterName=parameterValue

Subsequent query parameters are preceded by an ampersand, using the following format:

&parameterName=parameterValue

For example, to get all identities who are marked as external ordered by their company membership, use the following request:

https://<Hostname>/AppServer/api/entities/person?where=IsExternal%3D0&orderBy=CompanyMember

NOTE: If a parameter is not shown in a request’s URI format with a slash, it is a query parameter; the URI format for a request shows only the path parameters. The description that follows each URI format provides information on the query parameters, if any.

Query parameters to be used in WHERE clauses and predefined WHERE clauses can be provided in the form @paramname=value. Per default they have the type string. Additionally, it is possible to pass the type with the name: @otherParam[int]=3. Types originate from DbVal class.

HTTP request methods

Guidelines and conventions > HTTP request methods

Depending on the HTTP request, use one of the following HTTP request methods:

Get: Use for requests that retrieve elements from the application server.
Put: Use for requests that change elements on the application server.
Post: Use for requests that create an element on the application server.
Delete: Use for request that delete an element on the application server.

The request methods Put and Post will also be used if:

The number or the size of the parameters would lead to problems in the URL.
The type of parameter would lead to problems in the URL.

Each request description specifies which HTTP request method to use.

To use these request methods on an application server they must be permitted by the web server.

Request formats

Guidelines and conventions > Request formats

Request body values have to be formatted as JSON and the request content type application/json has to be set.

Response formats

Guidelines and conventions > Response formats

Code-issued requests to the API should always return JSON, based on the request headers.

To return JSON output

Set the Accept header in the request to application/json.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem