Response codes
Responses that are sent from the REST API use the following codes. If queries fail, an explanatory error message is displayed.
|
200 |
Query successful. |
|
204 |
Query successful. Response has no content. |
|
401 |
Access not authorized. The session must be authorized first. |
|
404 |
The given resource could not be found. |
|
405 |
The HTTP method used is not allowed for this query. |
|
500 |
A server error occurred. The error message is sent with the response. On the ground of security, a detailed error message is not included in the response. For more information, see the application log file on the server. |
Related topics
Avoiding deadlocks
API development includes a lot of asynchronous code with async/await constructs. To avoid deadlocks, use the ConfigureAwait(false) method for every await keyword.
For more information, see https://blog.stephencleary.com/2012/07/dont-block-on-async-code.html and https://devblogs.microsoft.com/dotnet/configureawait-faq/.
Examples and help – Software Development Kit
Examples and help – Software Development Kit
To make it easier for you to start developing your API, One Identity provides a Software Development Kit (SDK) with lots of commented code example.
The SDK can be found on the installation medium in the directory QBM\dvd\AddOn\ApiSamples.
Implementing your own APIs
Implementing your own APIs
To implement your own APIs, you can create API plugins.
The API Server loads all DLLs matching the *.CompositionApi.Server.PlugIn.dll naming scheme and deploys the API definitions contained therein.
To implement your own APIs, the following options are available:
Detailed information about this topic
