canonical: https://jentic.com/apis/qlik.com/qlik

# Qlik Sense API

Business analytics and data visualization. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get access token, list resources. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Get access token
- List resources
- Access Qlik Sense API analytics resources via REST API

## Use cases

### Analytics Operations

Use the Qlik Sense API to perform analytics operations programmatically. The API provides 3 endpoints covering core functionality including get access token, list resources, get resource.

Example prompt: Call POST `/auth/token` to get access token

### Automated Authentication Management

Automate authentication operations by combining multiple Qlik Sense API endpoints. Agents can list resources and then get resource in a single workflow.

Example prompt: Call GET /resources to list resources, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Qlik Sense API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Get access token |
| GET | `/resources` | List resources |
| GET | `/resources/{id}` | Get resource |

## Key resources

- **Authentication** — Authentication and authorization
- **Resources** — Resource management

## Why Jentic

- **Setup:** Wiring the Qlik Sense API by hand means sending your key in the Authorization header, exchanging it for an access token, and handling resource calls yourself. Through Jentic you install once, import the Qlik Sense API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Qlik Sense puts the resource id in the URL path (`/resources/{id}`), so a rule can pin your agent to one resource: it can read that resource and nothing else. You choose the operations it may call, so token issuance is not included unless you add it.
- **Credential handling:** Your Qlik Sense key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list resources' or 'get a resource by id', and Jentic returns the matching Qlik Sense operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Qlik Sense API use?

The Qlik Sense API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get access token with the Qlik Sense API?

Yes. Use the POST `/auth/token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Qlik Sense API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get access token'. Jentic returns the matching Qlik Sense API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Qlik Sense API have?

The Qlik Sense API exposes 3 endpoints covering authentication, resources operations.

### Can I limit what my agent is allowed to do with the Qlik Sense API?

Yes. Because you run Jentic One yourself, your own rules decide which Qlik Sense operations and credentials the agent may use. Since the resource id sits in the URL path (`/resources/{id}`), a rule can pin the agent to a single resource so it can read that one resource with GET `/resources/{id}` and nothing else. You choose the operations it may call, so token issuance via POST `/auth/token` stays excluded unless you explicitly allow it.