Skip to content
English
Log a Support Call Customer portal
  • There are no suggestions because the search field is empty.

Troubleshoot IntelliFront BI API Integrations

Find the failing stage of an IntelliFront BI API integration and use the appropriate connection, access, response and report-execution checks.

Start with the step that failed: connecting to the installation, authenticating, accessing content, saving configuration, processing a report job or delivering its output. Test that step before repeating the whole workflow.

Connection or certificate errors

Confirm the installation root, any IIS application path, the protocol and network access from the integration host. For HTTPS, check hostname matching, certificate validity and trust. Follow Connect to your IntelliFront installation.

Authentication or access failures

Check the token, chosen user or service-client flow, operation permissions and required current-user context. Successful sign-in does not grant every management permission. Review authentication and content access.

If the operation is rejected by an installation licensing check, ask your administrator to review the installation’s licence and configuration.

Unexpected responses or save results

Use the operation’s documented response shape. IntelliFront operations can return bare objects, arrays or wrapped results. Check application-level errors and endpoint-specific success rules as well as the HTTP status.

For example, Dataset Save can return a non-GUID error string with HTTP 200. Validate the saved identifier and read the configuration back. See Handle API requests, responses and errors.

A report job is queued or output is missing

Confirm the selected Gizmo and its enabled state, reporting-source access, backend services and destination credentials. Review Client Service Status, Gizmo History and the Error Log. Compare error timestamps with the run being investigated.

Use Troubleshoot API and report execution for the queue and error operations. Confirm the report output at its destination before treating the workflow as successful.

Reporting data appears old

Check dataset refresh history and dashboard cache age separately from viewer refresh. The monitoring calls do not start a dataset refresh.

Before retrying or contacting Support

Reconcile uncertain saves and report submissions before repeating them. Retain the installed build, method and operation, timestamp with time zone, relevant IDs, HTTP status and a sanitised response summary. Exclude passwords, client secrets, active tokens and customer report data.

For future recovery planning, follow Build a reliable API integration. For a first connection, return to Get Started with the IntelliFront BI API.