4.1.5.1. System Metadata – Babelway

System metadata are automatically made available to all of your channels. See the Metadata chapter for understanding how Metadata can be used. This page lists available system metadata.

Available on all messages

com_babelway_messaging_context_message_uuid : The message key. Ex : 188e6721-0131-4e8c-979f-991c2e561c07.
com_babelway_messaging_context_original_message_uuid : When multiple channels are used to process an incoming message, refers to the message key of the original message of the flow.
com_babelway_messaging_context_hubId : The id of the environment that is processing your message. Ex: 25321.
com_babelway_messaging_context_channelId : The id of the channel that is processing your message. Ex: 497959.
com_babelway_messaging_context_fromId : the id of the gateway IN of the message.
com_babelway_messaging_context_messageDefinitionInId : the id of the MessageDefinition IN of the message.
com_babelway_messaging_context_transformationId : the id of the transformation of the message.
com_babelway_messaging_context_messageDefinitionOutId : the id of the MessageDefinition OUT of the message.
com_babelway_messaging_context_toId : the id of the gateway OUT of the message.
com_babelway_messaging_context_message : The content of the message that is being processed. This metadata is usually quite big, as it is a whole file content (xml, csv, pdf, ...).
com_babelway_messaging_context_receiveTimestamp : When the current message was received, in epoch format (number of milliseconds since 1/1/1970).
com_babelway_messaging_context_receiveDay : When the current message was received, in format yyyyMMdd. Ex: 20240911.
com_babelway_messaging_context_receiveTime : When the current message was received, in format yyyyMMdd-hhmmss. Ex: 20240911-113446.
com_babelway_messaging_context_receiveTime_extended : When the current message was received, in format yyyyMMdd-hhmmss-SSS. Ex: 20240911-113446-123.
com_babelway_messaging_context_message_reference : The message reference. Ex: B12345. See section about message reference in Metadata page for more details about message reference.
com_babelway_messaging_context_in_filename : The file name of the input message. Ex: Invoice12345.xml .
com_babelway_messaging_context_in_filename_no_extension : the file name of the input message, without its extension. Ex : Invoice12345 .
com_babelway_messaging_context_out_filename : The file name of the output message. Ex: Invoice12345.xml .
com_babelway_messaging_context_in_size : The size of the input file.
com_babelway_messaging_context_out_size : The size of the output file.
com_babelway_messaging_context_testMessage : 'true' if the message is a test case.
com_babelway_messaging_context_gatewayInMessageKey : The gateway in message key of the message.
com_babelway_messaging_context_gatewayOutMessageKey : The gateway out message key of the message.
com_babelway_messaging_context_gatewayInMessageStatus : the gateway in message status of the message.
com_babelway_messaging_context_gatewayOutMessageStatus : the gateway out message status of the message.
com_babelway_messaging_context_in_md5 : a md5 hash of the message In (the content of the message before the start of the processing).

On messages received by EMAIL

com_babelway_messaging_context_mail_from : The sender (from) of the email through which we received the message. Ex : sender@yourprovider.com .
com_babelway_messaging_context_mail_to : The recipient (to) of the email through which we received the message. It should be the email configured in your gateway IN. Ex : invoices@mycompany.com .
com_babelway_messaging_context_mail_subject : The subject of the email through which we received the message. Ex: Invoice 12345.
com_babelway_messaging_context_mail_body : The content (body) of the email through which we received the message.
com_babelway_messaging_context_mail_message_id : the id of the email through which we received the message.
com_babelway_messaging_context_mail_dkimstatus : The result of the dkim check of the received email. Ex : SUCCESS.
com_babelway_messaging_context_mail_spfstatus : The result of the SPF check of the received email. Ex : "pass (spfCheck: domain of tradeshift.com designates 209.85.128.53 as permitted sender) client-ip=209.85.128.53; envelope-from=bertrand.lanneau@tradeshift.com; helo=tradeshift.com;".

On messages received by AS2

com_babelway_messaging_context_as2_from : the AS2 sender address. Ex : C4NETBE.
com_babelway_messaging_context_as2_to : the AS2 receiver address. Ex : BABELWAY_AS2_25010.
com_babelway_messaging_context_as2_receive_date : the receiving date of the AS2 message. The format will be an epoch (number of milliseconds since 1/1/1970).
com_babelway_messaging_context_as2_send_date : the sending date of the AS2 message. The format will be an epoch (number of milliseconds since 1/1/1970).
com_babelway_messaging_context_as2_message_id : the AS2 Id of the message. Ex : d19bc8_1210d8ea134_-45ec @C4NETBE_host.
com_babelway_messaging_context_as2_subject : the AS2 subject.
com_babelway_messaging_context_as2_type : the content type used in AS2. Ex : application/octet-stream.

On messages received by AS4

com_babelway_messaging_context_as4_from : the AS4 sender address.
com_babelway_messaging_context_as4_to : the AS4 receiver address.
com_babelway_messaging_context_as4_receive_date : the receiving date of the AS4 message. The format will be an epoch (number of milliseconds since 1/1/1970).
com_babelway_messaging_context_as4_message_id : the AS2 Id of the message.
com_babelway_messaging_context_as4_conversation_id : the AS4 converstaion Id.
com_babelway_messaging_context_as4_action : the AS4 action.
com_babelway_messaging_context_as4_service : the AS4 service

On message created by an aggregator

com_babelway_messaging_context_aggregator_group_by : The value based on which message were aggregated. See details about the group by parameter of the aggregator gateway in the dedicated page.

On message created by a splitter

com_babelway_messaging_current_split_number : a numbering of the part, starting at 0. For example, if a file is split in 3 parts, they will have respectively values 0, 1 and 2 in this metadata.

On message received by a REST gateway IN

rest_uri : the called URI. Ex : /sws/shipmentStatus/BE.json .
rest_action : the called action. Ex : shipmentStatus .
rest_format : the requested output format. Ex : json .