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

# Qminder API

Qminder is a waiting list management system for physical locations. Manage locations, lines, tickets, appointments, users, and webhooks. The API exposes 49 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get list of locations, get location details. Covers 49 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get list of locations
- Create a line at location
- Edit a line
- Access Qminder API developer tools resources via REST API

## Use cases

### Developer Tools Operations

Use the Qminder API to perform developer tools operations programmatically. The API provides 49 endpoints covering core functionality including get list of locations, get location details, get desks at location.

Example prompt: Call GET /locations to get list of locations

### Automated Locations Management

Automate locations operations by combining multiple Qminder API endpoints. Agents can get location details and then get desks at location in a single workflow.

Example prompt: Call GET `/locations/{id}` to get location details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Qminder 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 list of locations', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/locations` | Get list of locations |
| GET | `/locations/{id}` | Get location details |
| GET | `/locations/{id}/desks` | Get desks at location |
| POST | `/locations/{id}/lines` | Create a line at location |
| GET | `/locations/{id}/lines` | Get list of lines at location |
| POST | `/lines/{id}` | Edit a line |
| GET | `/lines/{id}` | Get line details |
| DELETE | `/lines/{id}` | Delete a line |

## Key resources

- **Locations** — Location management
- **Lines** — Line/queue management
- **Tickets** — Queue ticket operations
- **Appointments** — Appointment scheduling
- **Users** — User management

## 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:** 60 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/qminder.com/qminder/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 Qminder by hand means setting its X-Qminder-REST-API-Key header on every request and managing the api.qminder.com host and its errors yourself. Through Jentic you install once, import the Qminder API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Qminder puts the line and location id in the URL path (`/lines/{id}`, `/locations/{id}/lines`), so a rule can pin your agent to one location or line: it can read desks and create lines there and nothing else. You choose the operations it may call, so destructive ones like deleting a line are not included unless you add them.
- **Credential handling:** Your Qminder API 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 locations' or 'create a service line', and Jentic returns the matching Qminder operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Qminder API use?

The Qminder API uses an API key passed in the `X-Qminder-REST-API-Key` 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 list of locations with the Qminder API?

Yes. Use the GET /locations endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Qminder 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 list of locations through Jentic?

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

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

The Qminder API exposes 49 endpoints covering locations, lines, tickets operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Qminder operations and credentials the agent may use. Because Qminder puts the location and line id in the URL path, such as `/locations/{id}/lines` and `/lines/{id}`, you can pin the agent to a single location or line and let it read desks and create lines there and nothing else. You also choose which operations it may call, so a destructive one like DELETE `/lines/{id}` is left out unless you deliberately add it.