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
- application/json
Query Parameters
-
limit: integer(int32)
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.
-
offset: integer(int32)
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.
-
q: string
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'}
Response
Supported Media Types
- application/json
200 Response
Successful operation
Nested Schema : wiremessage
Type:
Show Source
object
-
ackState:
string
- correlatedMessages: array correlatedMessages
-
createdBy:
string
-
creationDate:
string
-
direction:
string
-
errorCode:
string
-
errorDetail:
string
-
errorSummary:
string
-
id:
string
-
instanceId:
string
-
links:
array links
-
messageType:
string
-
packedPayloadId:
string
-
packedPayloadSize:
string
-
payload:
object payload
-
payloadName:
string
-
processingResults:
array processingResults
-
source:
string
-
state:
string
-
tradingPartner:
string
-
transportName:
string
-
transportProperties:
object transportProperties
Additional Properties Allowed: additionalProperties
-
transportProtocol:
string
-
unpackedPayloadId:
string
-
unpackedPayloadSize:
string
-
updatedBy:
string
-
updatedDate:
string
-
url:
string
-
userDefinedId:
string
Nested Schema : action
Type:
Show Source
object
-
abortType:
string
-
activityChanges:
array activityChanges
-
assignees:
array assignees
-
comments:
string
-
correlationKeyChanges:
array correlationKeyChanges
-
dataObjectChanges:
array dataObjectChanges
-
faultActionType:
string
-
flowId:
integer(int64)
-
id:
string
-
instanceAttributeChanges:
array instanceAttributeChanges
-
processes:
array processes
-
type:
string
400 Response
Malformed parameters
412 Response
Pre condition failed
500 Response
Server error