How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Qminder Locations API

Manage physical service locations

Qminder Locations API is one of 7 APIs that Qminder publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Locations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 5 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.qminder.com.

5 operations 5 paths 6 schemas 3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.qminder.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Qminder Locations API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Qminder-REST-API-Key (sec0). By default, every request must be authenticated.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 3 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Locations 5

Manage physical service locations

POST
/locations
Create a location
create-location 1 param body → 201400
PATCH
/locations/{locationId}
Edit a location
edit-location 2 params body → 200400404
GET
/v1/locations/{id}
Get details of a location
get-details-of-a-location 1 param → 200
GET
/v1/locations/{id}/desks
Get desks of a Location
get-desks-of-a-location 1 param → 200
GET
/v1/locations
Get the list of locations
get-the-list-of-locations → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are LocationInputField (15 properties), LineRequest (4 properties), TimeRange (2 properties), TimeOfDay (2 properties). Each schema is shown below with its type and property counts.

LocationInputField
object
An input field to create with the location. Uses the same schema as POST /input-fields, but without location (auto-set) and visibleForLines (lines don't exist…
15 properties 8 required
LineRequest
object
A line (service) to create with the location.
4 properties 2 required
LineTranslationRequest
object
A name translation for a line.
2 properties 1 required
DaySchedule
object
Schedule for a single day. Either set businessHours or closed.
2 properties
TimeOfDay
object
A time of day.
2 properties
TimeRange
object
A time range with opening and closing times.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qminder-locations-api-openapi.yml Raw ↑

Other APIs Qminder publishes across the network.

Qminder Appointments API
Qminder Input Fields API
Qminder Lines API
Qminder Tickets API
Qminder Users API
Qminder Webhooks API
Where this information came from

This is an independent, third-party profile of Qminder Locations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.