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

TIBCO Groups API

Manage user groups

TIBCO Groups API is one of 26 APIs that TIBCO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Group. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and an API reference.

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

Requests are made against 2 base URLs: https://spotfire.cloud.tibco.com/api/rest/v1, https://{spotfire-server}/spotfire/api/rest/v1.

6 operations 3 paths 3 schemas 1 DELETE3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://integration.cloud.tibco.com/api/v1
Authentication
HTTP Bearer, HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 2

TIBCO Groups API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 bearer token for Spotfire API access
  • basicAuth — Basic authentication for on-premise Spotfire Server

Paths & Operations 6

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

Groups 6

Manage user groups

GET
/groups
List groups
listGroups → 200401
POST
/groups
Create a group
createGroup body → 201400401
GET
/groups/{groupId}
Get a group
getGroup 1 param → 200401404
DELETE
/groups/{groupId}
Delete a group
deleteGroup 1 param → 204401404
GET
/groups/{groupId}/members
List group members
listGroupMembers 1 param → 200401404
POST
/groups/{groupId}/members
Add a member to a group
addGroupMember 1 param body → 200400401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are User (7 properties), Group (5 properties), CreateGroupRequest (2 properties). Each schema is shown below with its type and property counts.

User
object
7 properties
CreateGroupRequest
object
2 properties 1 required
Group
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tibco-groups-api-openapi.yml Raw ↑

Other APIs TIBCO publishes across the network.

TIBCO Messaging API
TIBCO Agents API
TIBCO Analyses API
TIBCO Applications API
TIBCO Apps API
TIBCO Channels API
TIBCO Connections API
TIBCO Data Sources API
TIBCO Decision Tables API
TIBCO Deployments API
TIBCO Endpoints API
TIBCO Environments API
Where this information came from

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