ODAG apps
ODAG applications are accessible through a read-only API. Discover and list applications filtered by type: selection (entry points), template (source applications for generation), or generated (on-demand applications created from ODAG requests).
This API is read-only. All mutations on generated applications are performed through the ODAG Requests API.
Endpoints
Retrieves ODAG Analytics Applications filtered by type: selection (used as entry points), template (source Analytics Application for generation), or generated (Analytics Applications created via ODAG requests).
Facts
| Rate limit | Tier 1 (1000 requests per minute) |
Query Parameters
- appTypestringRequired
The type of ODAG Analytics Application.
Can be one of: "selection""template""generated"
Responses
200
Successful response.
- application/jsonobject
The response body for ODAG Analytics Applications.
application/json properties
- dataarray of objects
Condensed state of an Analytics Application returned in
statefor Link, LinkUsage, Request, and ODAG Apps GET calls.data properties
- idstringRequired
The system-assigned ID for an Analytics Application.
- namestringRequired
The name of an Analytics Application.
-
-
403
Forbidden.
- application/jsonobject
A standard error response containing a list of one or more errors.
application/json properties
- errorsarray of objects
A single error entry within an error response.
errors properties
- codestring
A unique code used to identify the template form of the message in i18n tables (language independent).
- metaobject
Additional metadata associated with an error.
meta properties
- statusCodeinteger
The HTTP status code for the error. Generally speaking, the following codes have these meanings:
200- Success,201- Success (object created),400- Error with user input,403- Authorization error (user lacks permission),404- Object not found,409- Attempt to change an object using an obsolete last ModifiedDate.
-
- titlestring
- detailstring
The message describing the error.
-
- traceIdstring
A unique ID of the trace which the error occurred in. Makes it possible to locate involved services and find log messages from the time of the error.
-
// qlik-api has not implemented support for `GET /api/analytics/odag-apps` yet.// In the meantime, you can use fetch like this:
const response = await fetch( '/api/analytics/odag-apps', { method: 'GET', headers: { 'Content-Type': 'application/json', }, },)This API is not included yet in qlik-clicurl "https://{tenant}.{region}.qlikcloud.com/api/analytics/odag-apps" \-H "Authorization: Bearer <access_token>"Example Response
{ "data": [ { "id": "string", "name": "appname" } ]}