ODAG settings
ODAG settings control tenant-level on-demand analytics generation configuration, including retention policies and resource limits. Settings are retrieved and updated as a singleton resource at the tenant level.
ODAG settings can only be modified by users assigned the TenantAdmin role.
Endpoints
Retrieves ODAG settings, including feature enablement status. Available only to administrators.
Facts
| Rate limit | Tier 1 (1000 requests per minute) |
Responses
200
ODAG settings retrieved successfully.
- application/jsonobject
The state of the ODAG settings available for users assigned the
TenantAdminrole to view and configure.application/json properties
- odagEnabledboolean
Whether the ODAG feature is enabled.
- dynamicViewEnabledboolean
Whether the dynamic view feature is enabled.
-
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.
-
500
Internal system error accessing ODAG settings.
- 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-settings` yet.// In the meantime, you can use fetch like this:
const response = await fetch( '/api/analytics/odag-settings', { method: 'GET', headers: { 'Content-Type': 'application/json', }, },)This API is not included yet in qlik-clicurl "https://{tenant}.{region}.qlikcloud.com/api/analytics/odag-settings" \-H "Authorization: Bearer <access_token>"Example Response
{ "odagEnabled": true, "dynamicViewEnabled": true}Modifies ODAG settings such as feature enablement. Available only to administrators. Changes apply immediately to all ODAG operations.
Facts
| Rate limit | Tier 2 (100 requests per minute) |
Request Body
RequiredA JSON payload containing the content for the new settings.
- application/jsonobject
An object that defines the properties of ODAG settings to be modified.
application/json properties
- odagEnabledboolean
- dynamicViewEnabledboolean
-
Responses
200
ODAG settings updated successfully.
- application/jsonobject
The state of the ODAG settings available for users assigned the
TenantAdminrole to view and configure.application/json properties
- odagEnabledboolean
Whether the ODAG feature is enabled.
- dynamicViewEnabledboolean
Whether the dynamic view feature is enabled.
-
403
Access denied. You lack permission to modify ODAG settings.
- 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.
-
500
Internal system error accessing ODAG settings.
- 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 `PUT /api/analytics/odag-settings` yet.// In the meantime, you can use fetch like this:
const response = await fetch( '/api/analytics/odag-settings', { method: 'PUT', headers: { 'Content-Type': 'application/json', }, body: JSON.stringify({ odagEnabled: true, dynamicViewEnabled: true, }), },)This API is not included yet in qlik-clicurl "https://{tenant}.{region}.qlikcloud.com/api/analytics/odag-settings" \-X PUT \-H "Content-type: application/json" \-H "Authorization: Bearer <access_token>" \-d '{"odagEnabled":true,"dynamicViewEnabled":true}'Example Response
{ "odagEnabled": true, "dynamicViewEnabled": true}Checks whether the current user has permission to modify ODAG settings.
Facts
| Rate limit | Tier 1 (1000 requests per minute) |
Responses
200
Permission check completed successfully.
- application/jsonobject
An object used to inform the caller whether the current user has privilege to update ODAG settings.
application/json properties
- canUpdateSettingsboolean
-
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-settings/canupdate` yet.// In the meantime, you can use fetch like this:
const response = await fetch( '/api/analytics/odag-settings/canupdate', { method: 'GET', headers: { 'Content-Type': 'application/json', }, },)This API is not included yet in qlik-clicurl "https://{tenant}.{region}.qlikcloud.com/api/analytics/odag-settings/canupdate" \-H "Authorization: Bearer <access_token>"Example Response
{ "canUpdateSettings": true}