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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
QGenda

QGenda Location API

The Location API from QGenda — 18 operation(s) for location.

Documentation Provider Profile APIs.io OpenAPI GitHub

QGenda Location API is one of 27 APIs that QGenda publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Location. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 25 operations across 18 paths. It is described by OpenAPI 3.2.0, at version 2.

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

25 operations 18 paths 0 schemas 7 DELETE4 GET8 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2
Base URL
https://api.qgenda.com/v2
Authentication
HTTP Bearer
Contact
QGenda Support
Resource Areas
1

Authentication & Security 1

QGenda Location API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Access token returned by POST /v2/login. Send as Authorization: bearer .

Paths & Operations 25

Across 18 paths, the API surfaces 25 operations — 7 DELETE, 4 GET, 8 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Location 25
GET
/v2/location
Location
getLocation → 200401
POST
/v2/location
Location
postLocation body → 200401
PUT
/v2/location/{locationId}
Location
putLocationLocationId 1 param body → 200401
DELETE
/v2/location/{locationId}
Location
deleteLocationLocationId 1 param → 200401
GET
/v2/credentialing/locations
Credentialing/Location
getCredentialingLocations → 200401
POST
/v2/credentialing/location
Credentialing/Location
postCredentialingLocation body → 200401
PUT
/v2/credentialing/location/{locationId}
Credentialing/Location/LocationId
putCredentialingLocationLocationId 1 param body → 200401
PUT
/v2/credentialing/location/contacts/{contactKey}/location/{locationId}/
Credentialing/Location/Contacts
putCredentialingLocationContactsContactKeyLocationLocationId 2 params body → 200401
DELETE
/v2/credentialing/location/contacts/{contactKey}/location/{locationId}/
Credentialing/Location/Contacts
deleteCredentialingLocationContactsContactKeyLocationLocationId 2 params → 200401
GET
/v2/location/{locationId}/staff
Location/Staff
getLocationLocationIdStaff 1 param → 200401
POST
/v2/location/{locationId}/staff
Location/Staff
postLocationLocationIdStaff 1 param body → 200401
POST
/v2/location/{locationId}/staff/{staffId}/FTE
Location/Staff/FTE
postLocationLocationIdStaffStaffIdFTE 2 params body → 200401
POST
/v2/location/{locationId}/staff/{staffId}/tag
Location/Staff/Tag
postLocationLocationIdStaffStaffIdTag 2 params body → 200401
DELETE
/v2/location/{locationId}/staff/{staffId}/tag
Location/Staff/Tag
deleteLocationLocationIdStaffStaffIdTag 2 params → 200401
PUT
/v2/location/{locationId}/staff/{staffId}
Location/Staff
putLocationLocationIdStaffStaffId 2 params body → 200401
DELETE
/v2/location/{locationId}/staff/{staffId}
Location/Staff
deleteLocationLocationIdStaffStaffId 2 params → 200401
POST
/v2/Credentialing/Locations/Providers
Credentialing/Locations/Providers
postCredentialingLocationsProviders body → 200401
PUT
/v2/credentialing/locations/{locationId}/staff/{staffId}
Credentialing/Locations/Staff
putCredentialingLocationsLocationIdStaffStaffId 2 params body → 200401
DELETE
/v2/location/{locationId}/staff/{staffId}/credential
Location/Staff/Credential
deleteLocationLocationIdStaffStaffIdCredential 2 params → 200401
GET
/v2/location/{locationId}/tasks
Location/Tasks
getLocationLocationIdTasks 1 param → 200401
POST
/v2/location/{locationId}/task
Location/Task
postLocationLocationIdTask 1 param body → 200401
PUT
/v2/location/{locationId}/task/
Location/Task
putLocationLocationIdTask 1 param body → 200401
DELETE
/v2/location/{locationId}/task/{taskId}
Location/Task
deleteLocationLocationIdTaskTaskId 2 params → 200401
POST
/v2/location/{locationId}/tag
Location/Tag
postLocationLocationIdTag 1 param body → 200401
DELETE
/v2/location/{locationId}/tag
Location/Tag
deleteLocationLocationIdTag 1 param → 200401

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qgenda-location-api-openapi.yml Raw ↑

Other APIs QGenda publishes across the network.

QGenda Company API
AE Profile APIs.io
QGenda Contacts API
AE Profile APIs.io
QGenda Corporate Entities API
AE Profile APIs.io
QGenda Credit Allocation API
AE Profile APIs.io
QGenda Daily API
AE Profile APIs.io
QGenda Daily Case API
AE Profile APIs.io
QGenda Integration API
AE Profile APIs.io
QGenda Locations API
AE Profile APIs.io
QGenda Login API
AE Profile APIs.io
QGenda Notification List API
AE Profile APIs.io
QGenda Organization API
AE Profile APIs.io
QGenda Pay Code API
AE Profile APIs.io
#Location
← Back to Q APIs
API Details
ID
qgenda:qgenda-location-api
Base URL
https://api.qgenda.com/v2
Docs
https://restapi.qgenda.com/
Provider
QGenda
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=qgenda-location-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/qgenda-location-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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