Retrieve Wire Messages

get

/ic/api/b2b/v1/monitoring/wiremessages

Retrieves a list of wire messages along with information such as message type, state, direction, protocol and trading partner. Wire messages represent the technical exchange of messages from/to the host company and trading partners, such as an encrypted and signed AS2 message.

Request

Supported Media Types
Query Parameters
  • Use with the limit parameter for paginating through the returned results. The offset is the starting point from which to return records. For example, offset=3&limit=16 indicates to list wire messages starting at the 4th item, and the list will contain 16 items.
  • Use with the offset parameter for paginating through the returned results. Default is 0. The limit is the maximum number of items to return at one time. For example, offset=3&limit=16 indicates to list wire messages starting at the 4th item, and the list will contain 16 items.
  • Filter parameters.

    • timewindow: 1h, 6h, 1d, 2d, 3d, RETENTIONPERIOD. Default value is 1h.
    • direction: Message direction. Valid values are INBOUND and OUTBOUND.
    • id: Wire message identifier.
    • startdate: Custom time range start date/time in UTC format for filtering messages.
    • enddate: Custom time range end date/time in UTC format for filtering messages.
    • status: Message status.
    • transportprotocol: Message transport protocol. Valid values are AS2 and FTP.
    • instanceId: Integration instance identifier.
    • errorcode: Value of b2b error code.
    • tradingpartnerid: Trading partner identifier.
    • messagetype: Message type. Valid values are WIRE and MDN.
    • userdefinedid: A message identifier at the wire protocol level, if one is defined for the transport type. For AS2 transport, this is set to the AS2 message Identifier. For FTP transport this field is not available.

    Example:

    {startdate:'2020-07-09 07:00:00', enddate:'2020-07-09 21:25:00', id:'0AC415941776251CB5E0000026D27C45', direction:'INBOUND', messagetype:'WIRE'}
Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : wiremessages
Type: object
Show Source
Nested Schema : items
Type: array
Show Source
Nested Schema : wiremessage
Type: object
Show Source
Nested Schema : correlatedMessages
Type: array
Show Source
Nested Schema : payload
Type: object
Show Source
Nested Schema : processingResults
Type: array
Show Source
Nested Schema : transportProperties
Type: object
Additional Properties Allowed
Show Source
Nested Schema : CorrelatedMessage
Type: object
Show Source
Nested Schema : action
Type: object
Show Source
Nested Schema : comment
Type: object
Show Source
Nested Schema : identities
Type: array
Show Source
Nested Schema : activityChanges
Type: array
Show Source
Nested Schema : assignees
Type: array
Show Source
Nested Schema : correlationKeyChanges
Type: array
Show Source
Nested Schema : dataObjectChanges
Type: array
Show Source
Nested Schema : instanceAttributeChanges
Type: array
Show Source
Nested Schema : processes
Type: array
Show Source
Nested Schema : FlowChangeItemReq
Type: object
Show Source
Nested Schema : correlationKeyChanges
Type: array
Show Source
Nested Schema : dataObjectChanges
Type: array
Show Source
Nested Schema : instanceAttributeChanges
Type: array
Show Source
Nested Schema : DataVariable
Type: object
Show Source
Nested Schema : QName
Type: object
Show Source
Nested Schema : identity
Type: object
Discriminator: type
Show Source

400 Response

Malformed parameters

412 Response

Pre condition failed

500 Response

Server error
Back to Top