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

Apache Guacamole Connections API

Remote desktop connection management

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

This API exposes 1 JSON Schema definition.

Tagged areas include Connections. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 1 JSON Schema.

This API exposes 5 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.6.0.

Requests are made against a single base URL, http://localhost:8080/guacamole.

5 operations 2 paths 1 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.6.0
Base URL
http://localhost:8080
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

Apache Guacamole Connections API declares 1 security scheme for authenticating requests. An API key is passed in the header as Guacamole-Token (GuacamoleToken).

  • GuacamoleToken — Authentication token obtained from POST /api/tokens

Paths & Operations 5

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

Connections 5

Remote desktop connection management

GET
/api/session/data/{dataSource}/connections
Apache Guacamole List Connections
listConnections 2 params → 200403
POST
/api/session/data/{dataSource}/connections
Apache Guacamole Create Connection
createConnection 2 params body → 200403
GET
/api/session/data/{dataSource}/connections/{connectionId}
Apache Guacamole Get Connection
getConnection 3 params → 200404
PUT
/api/session/data/{dataSource}/connections/{connectionId}
Apache Guacamole Update Connection
updateConnection 3 params body → 204404
DELETE
/api/session/data/{dataSource}/connections/{connectionId}
Apache Guacamole Delete Connection
deleteConnection 3 params → 204404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Connection (6 properties). Each schema is shown below with its type and property counts.

Connection
object
Remote desktop connection configuration
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

apache-guacamole-connections-api-openapi.yml Raw ↑

Other APIs Apache Guacamole publishes across the network.

Apache Guacamole JavaScript Client API
Apache Guacamole Active Connections API
Apache Guacamole Authentication API
Apache Guacamole History API
Apache Guacamole User Groups API
Apache Guacamole Users API
Where this information came from

This is an independent, third-party profile of Apache Guacamole Connections 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.