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

# Smartlookcom Smartlook API

Smartlook REST API for managing sessions, visitors, events, funnels, and webhooks. Rate limits: Free plan 20 req/hr, Paid plans 100 req/hr, REST API add-on 1,000 req/hr. Inactive tokens expire after 90 days. The API exposes 23 endpoints secured with bearer authentication.

## For AI agents

Programmatically search sessions, get session details. Covers 23 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Search sessions
- Get session details
- Delete visitor
- Query and filter Smartlook API records by parameters
- Monitor Smartlook API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Smartlook API to perform identity auth operations programmatically. The API provides 23 endpoints covering core functionality including search sessions, get session details, get session public link.

Example prompt: Call POST `/api/v1/sessions` to search sessions

### Automated sessions Management

Automate sessions operations by combining multiple Smartlook API endpoints. Agents can get session details and then get session public link in a single workflow.

Example prompt: Call GET `/api/v1/sessions/{id}` to get session details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Smartlook 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 bearer tokens manually.

Example prompt: Search Jentic for 'search sessions', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/sessions` | Search sessions |
| GET | `/api/v1/sessions/{id}` | Get session details |
| GET | `/api/v1/sessions/{id}/public` | Get session public link |
| GET | `/api/v1/visitors/{id}` | Get visitor details |
| DELETE | `/api/v1/visitors/{id}` | Delete visitor |
| GET | `/api/v1/visitors/{id}/sessions` | Get visitor sessions |
| GET | `/api/v1/visitors/{id}/events` | Get visitor events |
| POST | `/api/v1/visitors/search` | Search visitors |

## Key resources

- **sessions** — Operations related to sessions
- **visitors** — Operations related to visitors
- **events** — Operations related to events
- **funnels** — Operations related to funnels
- **webhooks** — Operations related to webhooks

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 54 / 100
- **View full report:** https://jentic.com/apis/smartlookcom/smartlookcom/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Smartlook by hand means handling its bearer auth, resolving the right region host (api.{region}.smartlook.cloud, defaulting to eu), and managing retries yourself. Through Jentic you install once, import the Smartlook API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Smartlook puts the visitor and session id in the URL path (`/api/v1/visitors/{id}`, `/api/v1/sessions/{id}`), so a rule can pin your agent to one visitor: it can read that visitor's sessions and events. You choose the operations it may call, so deleting a visitor is not included unless you add it.
- **Credential handling:** Your Smartlook token 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 'find a visitor's sessions' or 'search recorded sessions', and Jentic returns the matching Smartlook operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Smartlook API use?

The Smartlook API uses a Bearer token 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 search sessions with the Smartlook API?

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

### What are the rate limits for the Smartlook 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 search sessions through Jentic?

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

### How many endpoints does the Smartlook API have?

The Smartlook API exposes 23 endpoints covering sessions, visitors, events operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Smartlook operations and credentials the agent may use, and Smartlook puts the visitor and session id in the URL path (`/api/v1/visitors/{id}`, `/api/v1/sessions/{id}`), so you can pin the agent to a single visitor and let it read only that visitor's sessions and events. You pick the operations it can call, so a destructive call like DELETE `/api/v1/visitors/{id}` stays off limits unless you explicitly grant it. The stored bearer token is injected only when an allowed operation runs, so the agent never sees the raw secret or reaches endpoints you have not approved.