...
Page Properties | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
Resources & Remarks Modification History
|
As of Version | product version 2022 Spring | component version | ||||||||
---|---|---|---|---|---|---|---|---|---|
Request Method | GET | ||||||||
Response Format | JSON | ||||||||
Description |
With this information, client applications can present the correct a selection list of object types on the UI that are available relevant for the individual userslogged-in user. Thus, the users will see only those object types that are relevant available to them. Those selection lists may differ for the different actions CREATE, READ, WRITE, or DELETE. The response body is a JSON structure listing all object types for the corresponding action as shown in the example below. The composition of the object type IDs including the usage of prefixes is described in the schema documentation article. Response HTTP status codes:
Internally, the endpoint calls the search service's endpoint GET /search/api/search/dsl/check. | ||||||||
Request Example |
no request body | ||||||||
Response Example |
|
...