Message Type Library

Every message sent or received in EchoStream must have a Message Type associated with it. This allows for deep auditing of messages as they pass through your Tenant's processing network and also allows for templated Transformer and Bitmapper functions, giving users that are using the Message Types a head start.

Your Tenant maintains a library of Message Types; this library may be found in the Message Types tab in your Tenant settings.

System Message Types

System Message Types are provided and maintained by EchoStream and always begin with the prefix echo.. You may use any of these Message Types in your Tenant. For a list of System Message Type, please refer to your Tenant's Message Types library.

Tenant Message Types

Sometimes the System Message Types simply aren't specific enough for your processing use cases.

For example, you may be integrating an application that emits a very specific JSON format and the system-provided echo.json Message Type is simply too generic (e.g. - doesn't allow deep auditing, or requires too much code each time you use it, or doesn't provide the specific Python package that you use to process your JSON).

In this case, you can create a custom Message Type for your Tenant (requires admin or higher role). Once this new Message Type is created, all Users in your Tenant can then use it in Nodes within your processing network.