Qminder API
✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey49 EndpointsREST
For Agents
Programmatically get list of locations, get location details. Covers 49 operations with apiKey authentication.
Use for: I need to list of locations, I want to location details, Search for desks at location, Find all a line at location
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
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.
Install Jentic One Beta
Connect the Qminder API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Qminder API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Qminder API.
Get list of locations
Create a line at location
Edit a line
Access Qminder API developer tools resources via REST API
Use Cases
Patterns agents use Qminder API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'get list of locations', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
49 endpoints — qminder is a waiting list management system for physical locations.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Qminder API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get list of locations') and Jentic returns the matching Qminder API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Qminder API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Qminder API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED