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

Enterprise messaging API supporting EMS (Enterprise Message Service) and FTL (Fast Transport Layer).

This event API exposes 12 operations across 6 channels, and defines 12 schemas. It is described by AsyncAPI 2.6.0, at version 1.0.

The API connects through 3 servers: ssl://messaging.cloud.tibco.com:7243 (jms), tcp://messaging.cloud.tibco.com:7222 (jms), https://messaging.cloud.tibco.com:8585 (https).

12 operations 6 channels 12 schemas

Metadata

The identity and technical contract details declared by the specification.

Specification
AsyncAPI 2.6.0
API Version
1.0
Base URL
https://messaging.cloud.tibco.com/api/v1
Resource Areas
1

Channels & Operations 12

Across 6 channels, the API surfaces 12 operations. Each is listed below with its action, channel, parameters, and response codes.

Channels 12
SUB
orders/created
Receive order created events
receiveOrderCreated body
PUB
orders/created
Publish order created event
publishOrderCreated body
SUB
orders/updated
Receive order update events
receiveOrderUpdated body
PUB
orders/updated
Publish order update event
publishOrderUpdated body
SUB
inventory/changed
Receive inventory change events
receiveInventoryChanged body
PUB
inventory/changed
Publish inventory change event
publishInventoryChanged body
SUB
notifications/alerts
Receive system alerts
receiveAlert body
PUB
notifications/alerts
Publish system alert
publishAlert body
SUB
integration/events
Receive integration events
receiveIntegrationEvent body
PUB
integration/events
Publish integration event
publishIntegrationEvent body
SUB
data/stream
Receive data stream messages
receiveDataStream body
PUB
data/stream
Publish data stream message
publishDataStream body

Messages & Schemas 12

The contract defines 12 schemas that model the data carried by its messages. The most detailed are InventoryEvent (8 properties), AlertEvent (7 properties), OrderEvent (6 properties), OrderStatusUpdate (5 properties). Each schema is shown below with its type and property counts.

OrderCreated
message
Notification that a new order has been created
OrderUpdated
message
Notification that an order status has changed
InventoryChanged
message
Notification that inventory levels have changed
Alert
message
System alert notification for operational monitoring
IntegrationEvent
message
General-purpose integration event for inter-application messaging
DataStreamMessage
message
High-throughput data stream message via FTL
OrderEvent
object
6 properties 3 required
OrderStatusUpdate
object
5 properties 3 required
InventoryEvent
object
8 properties 3 required
AlertEvent
object
7 properties 3 required
GenericEvent
object
3 properties 1 required
StreamPayload
object
3 properties

Specification

The full machine-readable AsyncAPI contract behind this narrative.

Source

tibco-messaging-asyncapi.yml Raw ↑
Where this information came from

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