Retrieve Business Messages
get
/ic/api/b2b/v1/monitoring/businessmessages
Retrieves a list of business messages along with information such as message type, state, direction and trading partner. Business messages represent individual documents or business transactions such as a purchase order.
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 business 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 business messages starting at the 4th item, and the list will contain 16 items.
-
q: string
Filter parameter.
- timewindow: 1h, 6h, 1d, 2d, 3d, RETENTIONPERIOD. Default value is 1h.
- direction: Message direction. Valid values are INBOUND and OUTBOUND.
- id: Business 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.
- instanceId: Integration instance identifier.
- errorcode: Value of error code.
- tradingpartnerid: Trading partner identifier.
- messagetype: Message type. Valid values are MSG and FA.
- userdefinedid: User defined Identifier for business message is the value for Application Message Identifier field for an outbound business message. This field is available for mapping in your outbound integration. If a value is set in the mapping, it is returned with the business message details.
- documenttype: Document type.
- documentstandard: Document standard.
- documentversion: Document version.
- identifiervalue: Value of business identifier.
- interchangecontrolnumber: Value of interchange control number.
- groupcontrolnumber: Value of group control number.
- transactioncontrolnumber: Value of transaction set control number.
Example:
{startdate:'2020-07-09 07:00:00', enddate:'2020-07-09 21:25:00', id:'0AC415941776251CB5E0000026D27C45', direction:'INBOUND', messagetype:'FA'}
Response
Supported Media Types
- application/json
200 Response
Successful operation
Nested Schema : businessmessage
Type:
Show Source
object
-
b2bPayloadId:
string
-
b2bPayloadSize:
string
-
canonicalPayloadId:
string
-
canonicalPayloadSize:
string
- correlatedMessages: array correlatedMessages
-
createdBy:
string
-
creationDate:
string
-
delimiter:
string
-
direction:
string
-
documentId:
string
-
documentStandard:
string
-
documentType:
string
-
documentVersion:
string
-
errorCode:
string
-
errorDetail:
string
-
errorSummary:
string
-
id:
string
-
identifiers:
object identifiers
Additional Properties Allowed: additionalProperties
-
instanceId:
string
-
links:
array links
-
messageType:
string
-
payload:
object payload
-
payloadName:
string
-
processingResults:
array processingResults
-
referenceToId:
string
-
state:
string
-
tradingPartner:
string
-
transportProperties:
object transportProperties
Additional Properties Allowed: additionalProperties
-
updatedBy:
string
-
updatedDate:
string
-
userDefinedId:
string
-
wireMessageId:
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