Overview

This page explains how Newline publishes messages to MQ topics, including the naming conventions, structure, and how clients can interpret and subscribe to these topics.

What Is Topic Publication?

Topic publication refers to how Newline sends event messages to specific MQ topics. Each topic is a logical channel that groups related events (e.g., transfers, transactions). Clients subscribe to these topics to receive real-time updates.

Topic Naming Convention

MQ topics follow a standardized format:

/topic/<client>.<environment>.<topic_name>

Example:\ /topic/neal.abc-enterprises.sandbox.transfer

<client>: Your organization or integration name
<environment>: sandbox or production
<topic_name>: The entity or event category (e.g., transfer, transaction)

How Topics Are Published

Newline publishes messages to durable topics using Apache ActiveMQ.
Each topic contains one or more event types (e.g., created, status_change, rtp_settlement).
Messages are published in JSON format and include:
- event_type
- details object
- event_id (for idempotency)

Example Topic Publication

Topic: /topic/neal.abc-enterprises.sandbox.transfer\ Payload:

{
  "event_type": "created",
  "details": {
    "transfer_uid": "Zb12cd34ef56gh7X",
    "usd_transfer_amount": "321.00",
    "customer_uid": "ab12cd34ef56gh78"
  }
}

Best Practices

Confirm topic names with your Newline Specialist during onboarding.
Use durable subscriptions to ensure message retention.
Implement idempotency using event_id.