MicroStrategy REST API

MicroStrategy REST API integration on the QodexAI API Network: This public API documentation features ready-to-use APIs, Collections, and more from MicroStrategy SDK.

MicroStrategy REST API | MicroStrategy REST API Workspace | API documentation

Get OIDC configuration for native clients.

If application auth mode is enabled, specify the ID of the custom application that initiate OIDC login.

applicationId

showAll

Comma-separated, top-level field whitelist that allows the client to selectively retrieve part of the response model. If specified, extra filtering is applied, and for top-level object (if root model is an array, each array element), only the listed fields are kept in the response. For example, "id,elements" keeps only the "id" field and whole "elements" array field, omitting all other fields in the top-level response model.

fields

"{\n    \"iams\": [\n        {\n            \"id\": \"8c1dd6a47fe84b7083becfdbb6a85536\",\n            \"issuer\": \"https://dev-19298591.okta.com\",\n            \"mstrIam\": false,\n            \"blockAutoProvisioning\": false,\n            \"endSessionEndpoint\": \"https://dev-19298591.okta.com/oauth2/v1/logout\",\n            \"nativeClientId\": \"0oa3q1fh8qjwcjNfZ5d7\",\n            \"redirectUri\": \"https://env-276686.customer.cloud.microstrategy.com/MicroStrategyLibrary/auth/oidc/login\",\n            \"scopes\": [\n                \"openid\",\n                \"profile\",\n                \"email\",\n                \"offline_access\"\n            ],\n            \"vendor\": {\n                \"name\": \"Okta\",\n                \"version\": \"0\"\n            },\n            \"default\": true,\n            \"metadata_endpoint\": \"https://dev-19298591.okta.com/.well-known/openid-configuration\",\n            \"authorization_endpoint\": \"https://dev-19298591.okta.com/oauth2/v1/authorize\",\n            \"token_endpoint\": \"https://dev-19298591.okta.com/oauth2/v1/token\",\n            \"userinfo_endpoint\": \"https://dev-19298591.okta.com/oauth2/v1/userinfo\",\n            \"jwks_uri\": \"https://dev-19298591.okta.com/oauth2/v1/keys\"\n        }\n    ]\n}"

200 OK

Get OIDC configuration for native clients. Configuration MicroStrategy REST API integration on the QodexAI API Network: This public API documentation features ready-to-use APIs, Collections, and more from MicroStrategy SDK.

Get OIDC configuration for native clients. Configuration MicroStrategy REST API | MicroStrategy REST API Workspace | API documentation

Configuration

Configuration MicroStrategy REST API integration on the QodexAI API Network: This public API documentation features ready-to-use APIs, Collections, and more from MicroStrategy SDK.

Configuration MicroStrategy REST API | MicroStrategy REST API Workspace | API documentation

This workspace contains two collections. To use the collections, you need to select an environment.

<ol>
<li>MicroStrategy REST API: Use it as API Documentation. It contains examples and built-in scripts to saved the context information after some requests, such as authToken, userId.</li>
<li>MicroStrategy REST API Workflows: It contains workflow examples. You can pick a folder and run all the requests.</li>
</ol>

The workspace contains a demo environment file. You can make a copy and change it to your environment.

Log your questions and feedback on <a href="https://github.com/MicroStrategy/rest-api-playground">https://github.com/MicroStrategy/rest-api-playground</a>

Contributions are welcome!

Github

Twitter

Developer Website

MicroStrategy REST API projects on the QodexAI API Network: This public API documentation features ready-to-use APIs, Collections, and more from MicroStrategy SDK.

Key	Datatype	Required	Description
applicationId	string		If application auth mode is enabled, specify the ID of the custom application that initiate OIDC login.
showAll	boolean
fields	null		Comma-separated, top-level field whitelist that allows the client to selectively retrieve part of the response model. If specified, extra filtering is applied, and for top-level object (if root model is an array, each array element), only the listed fields are kept in the response. For example, "id,elements" keeps only the "id" field and whole "elements" array field, omitting all other fields in the top-level response model.