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 Tickets API

Manage visitor queue entries

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

Tagged areas include Tickets. 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 21 operations across 19 paths. It is described by OpenAPI 3.2.0, at version 1.0.

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

21 operations 19 paths 0 schemas 1 DELETE3 GET1 PATCH16 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 Tickets 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 21

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

Tickets 21

Manage visitor queue entries

POST
/tickets
Create a ticket
create-ticket 1 param body → 201400404409
GET
/v1/tickets/search
Searching tickets
searching-tickets 11 params → 200
POST
/v1/tickets/count
Counting tickets
counting-tickets 8 params → 200
POST
/v1/tickets/{id}/call
Calling a ticket
calling-a-ticket 3 params → 200
POST
/v1/tickets/{id}/recall
Re-calling a ticket
re-calling-a-ticket 1 param → 200
PATCH
/tickets/{ticketId}
Editing a ticket
editing-a-ticket 2 params body → 200400404409
POST
/v1/tickets/{id}/markserved
Marking a ticket as served
marking-a-ticket-as-served 1 param → 200
POST
/v1/tickets/{id}/marknoshow
Marking a ticket as no-show
marking-a-ticket-as-no-show 1 param → 200
POST
/v1/tickets/{id}/cancel
Removing a ticket from the queue
removing-a-ticket-from-the-queue 2 params → 200
POST
/v1/tickets/{id}/returntoqueue
Returning a ticket to the queue
returning-a-ticket-to-the-queue 3 params → 200
POST
/v1/tickets/{id}/forward
Forwarding a ticket
forwarding-a-ticket 1 param body → 200
POST
/v1/tickets/{id}/labels/add
Adding a label
adding-a-label 1 param body → 200
POST
/v1/tickets/{id}/labels/remove
Removing a label
removing-a-label 1 param body → 200
POST
/v1/tickets/{id}/assign
Assigning a ticket to a user
assigning-a-ticket-to-a-user 1 param body → 200
POST
/v1/tickets/{id}/unassign
Un-assigning a ticket
un-assigning-a-ticket 1 param body → 200
POST
/v1/tickets/{id}/reorder
Reordering a ticket
reordering-a-ticket 1 param body → 200
GET
/v1/tickets/{id}
Get details of a ticket
get-details-of-a-ticket 2 params → 200
GET
/v1/tickets/{id}/messages
Get messages of a ticket
get-messages-of-a-ticket 1 param → 200
POST
/v1/tickets/{id}/messages
Sending an SMS message
sending-an-sms-message 1 param body → 200
POST
/v1/tickets/{ticketId}/fields/{inputFieldId}
Save ticket input field value
save-ticket-field 3 params body → 200400404409
DELETE
/v1/tickets/{ticketId}/fields/{inputFieldId}
Remove ticket input field value
remove-ticket-field 3 params → 200400404409

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qminder-tickets-api-openapi.yml Raw ↑

Other APIs Qminder publishes across the network.

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

This is an independent, third-party profile of Qminder Tickets 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.