Qlik Sense
APIs for Qlik Sense, a business intelligence and data analytics platform providing engine, repository, cloud, embedding, and data integration capabilities.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Qlik Sense the way a machine reads it — 41 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Qlik Sense scores 66.9/100 (strong), with a separate agent-readiness read of 60/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Qlik Sense
Each block below is one kind of artifact we hold for Qlik Sense. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Qlik Sense Engine API
WebSocket-based API for interacting with the Qlik Associative Engine, including data modeling, selections, and visualizations.
Qlik Sense Repository API
REST API for managing Qlik Sense repository objects including apps, streams, users, and security rules.
Qlik Sense Proxy API
REST API for session management and authentication through the Qlik Sense Proxy Service.
Qlik Data Integration API
REST API for managing data integration tasks, connections, and data pipelines.
Qlik Embedding API
JavaScript API for embedding Qlik Sense visualizations and mashups into web applications.
Qlik Sense Apps API
Manage Qlik Sense analytics applications including creating, copying, importing, exporting, publishing, and retrieving app metadata.
Qlik Sense Reloads API
Trigger and manage data reloads for apps to refresh data from connected sources.
Qlik Sense Spaces API
Manage spaces, which are logical containers within a tenant that control access for users and groups through role-based assignments.
Scroll within the panel for all 8 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Qlik Cloud REST API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Qlik Sense Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Qlik Sense Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Qlik Sense Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Qlik Sense API Rules
SPECTRALJSON Schema 22
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Qlik Sense App
JSON SCHEMAAppAttributes
JSON SCHEMAAppCopy
JSON SCHEMAAppCreate
JSON SCHEMAAppDataLineage
JSON SCHEMAAppDataMetadata
JSON SCHEMAAppPublish
JSON SCHEMAAppScript
JSON SCHEMAAppUpdate
JSON SCHEMAErrorResponse
JSON SCHEMAJsonPatch
JSON SCHEMAReload
JSON SCHEMAReloadCreate
JSON SCHEMAReloadList
JSON SCHEMAReloadLog
JSON SCHEMASpace
JSON SCHEMASpaceAssignment
JSON SCHEMASpaceAssignmentCreate
JSON SCHEMASpaceAssignmentList
JSON SCHEMASpaceCreate
JSON SCHEMASpaceList
JSON SCHEMASpaceUpdate
JSON SCHEMAScroll within the panel for all 22 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Qlik Sense Structure
JSON STRUCTURESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Qlik Sense — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/qlik-sense · machine-readable index on apis.io