EDIFACT Connector Record object

EDIFACT Connector Records correspond to the trading partner details of the Process Reporting page in the user interface. The EDIFACT Connector Record object contains EDIFACT-specific document information and user-defined tracked field information along with other fields.

<EDIFACTConnectorRecord>
    <account/>
    <executionId/>
    <atomId/>
    <dateProcessed/>
    <id/>
    <actionType/>
    <connectorType/>
    <connectorName/>
    <operationName/>
    <documentIndex/>
    <successful/>
    <size/>
    <errorMessage/>
    <customFields>
        <field1>value</field1>
        .
        .
        .
        <fieldN>value</fieldN>
    </customFields>
    <ackStatus/>
    <ackReport/>
    <senderID/>
    <receiverID/>
    <interchangeControlReference/>
    <messageType/>
    <messageReferenceNumber/>
    <interchangeDate/>
    <interchangeTime/>
    <ackRequested/>
    <version/>
    <release/>
    <controllingAgency/>
    <outboundValidationStatus/>
    <outboundValidationReport/>
</EDIFACTConnectorRecord>

Field	Type	Description
account	string	The ID of the account from which you ran this record.
executionId	string	The ID of the run.
atomId	string	The ID of the Runtime that processed this record.
dateProcessed	string	The processing date and time of this record. The format is yyyy-MM-dd'T'HH:mm:ss'Z', for example, 2018-08-08T15:32:00Z.
id	string	The ID of this record.
actionType	string	The type of action with which this record corresponds — Send for an outbound interchange, Get for an inbound interchange using the Disk, FTP, or SFTP communication method, or Listen for an inbound interchange using the AS2 or HTTP communication method.
connectorType	string	edifact is the connector type for any record.
connectorName	string	The value is Trading Partner for an EDIFACT trading partner Send operation, or Start for an EDIFACT trading partner Listen operation.
operationName	string	The name of the operation component that processed the record.
documentIndex	int	The numerical index of this record in the run.
successful	boolean	Whether the record is a success or an error.
size	long	The size, in bytes, of the document that corresponds to this record.
errorMessage	string	Any error message associated with this record.
customFields	string	Custom fields based on the fields configured on the Setup page’s Document Tracking tab in the user interface. The names of the fields are dependent upon your account setup.
ackStatus	string	The acknowledgment status — either Accepted, Received, or Rejected.
ackReport	string	The acknowledgment report.
senderID	string	For an outbound interchange, the UNB02, Interchange Sender ID, field value, which identifies the sender.
receiverID	string	For an inbound interchange, the UNB03, Interchange Receiver ID, field value, which identifies the receiver.
interchangeControlReference	string	The number that uniquely identifies the interchange.
messageType	string	The code identifying the type of message.
messageReferenceNumber	string	The unique message reference assigned by the sender.
interchangeDate	string	The date of preparation. The format is yyMMdd.
interchangeTime	string	The time of preparation. The format is HHmm.
ackRequested	string	The UNB09, the Acknowledgement Request field value, determines whether the sending trading partner requests a CONTRL message as functional acknowledgment. A value of 1 indicates there is an acknowledgment request. An empty value means there is no acknowledgment request.
version	string	The message type version number.
release	string	The message type release number.
controllingAgency	string	The controlling agency for the message type.
outboundValidationStatus	string	The outbound validation status — either Success, Error - Interchange, Error - Message, or N/A. For an outbound interchange for which the outbound validation option is not selected in the sending trading partner, the value is N/A. An inbound interchange omits this field.
outboundValidationReport	string	The outbound validation report. This report contains descriptions of errors present in the outbound interchange. If the outbound validation option is not selected in the sending trading partner, the value is N/A. An inbound interchange omits this field.

Supported operations

GET	QUERY	CREATE	UPDATE	EXECUTE	DELETE
Not supported	Supported	Not supported	Not supported	Not supported	Not supported

The following fields can be used as QUERY filters for the EDIFACT Connector Record object:

Field	Allowed values
executionId	Any string value
atomId	Any string value
dateProcessed	Date with the format yyyy-MM-dd'T'HH:mm:ss'Z', for example, 2018-08-08T15:32:00Z
id	Any string value
actionType	Send, Get, Listen
connectorType	edifact
connectorName	Trading Partner to filter by EDIFACT trading partner Send operations, Start to filter by EDIFACT trading partner Listen operations
operationName	Any string value
documentIndex	Any numeric value
successful	true, false
size	Any numeric value
errorMessage	Any string value
ackStatus	Accepted, Received, Rejected
ackReport	Any string value
senderID	Any string value
receiverID	Any string value
interchangeControlReference	Any string value
messageType	Any string value
messageReferenceNumber	Any string value
interchangeDate	Any string value
interchangeTime	Any string value
ackRequested	1 to filter by whether acknowledgment is requested, an empty value to filter by whether acknowledgment is not requested
outboundValidationStatus	Success, Error - Interchange, Error - Message, N/A
outboundValidationReport	Any string value

To filter by a customField, use the format customFields/fieldName as the filter property where fieldName is the element name of the custom field in the EDIFACT Connector Record structure. To get a list of the available custom fields see the Custom Tracked Field object documentation.

The operators allowed for the EDIFACT Connector Record object filters are:

BETWEEN
EQUALS
GREATER_THAN
GREATER_THAN_OR_EQUAL
LESS_THAN
LESS_THAN_OR_EQUAL
STARTS_WITH

However, it is important to note that the STARTS_WITH operator accepts values that do not include spaces only.

For general information about the structure of QUERY filters and how to handle paged results, see the Query filters and Query paging topics.

SOAP implementation

Send an HTTP Post to: https://api.boomi.com/api/rest/v1/{accountId}/EDIFACTConnectorRecord/query where {accountID} is the ID of the authenticating account for the request.

</bns:result>
  <bns:result xsi:type="bns:EDIFACTConnectorRecord">
   <bns:account>apiregression-PHRDMZ</bns:account>
   <bns:executionId>execution-ed44e114-b84f-4c32-b383-6d615b38a983-2025.04.16</bns:executionId>
   <bns:atomId>c4ae47d8-eeb3-47a5-a1b6-e9cd83eacd1e</bns:atomId>
   <bns:dateProcessed>2025-04-16T23:00:06Z</bns:dateProcessed>
   <bns:id>connector-4a661037-b189-4487-8788-6b7fee108915</bns:id>
   <bns:actionType>Send</bns:actionType>
   <bns:connectorType>edifact</bns:connectorType>
   <bns:connectorName>Trading Partner</bns:connectorName>
   <bns:operationName>shape4~6b66c92e-a63a-466c-9ce0-245800a58ec8</bns:operationName>
   <bns:documentIndex>2</bns:documentIndex>
   <bns:successful>true</bns:successful>
   <bns:size>44</bns:size>
   <bns:senderID>EDISENDER</bns:senderID>
   <bns:receiverID>EDIRECEIVER</bns:receiverID>
   <bns:interchangeControlReference>65</bns:interchangeControlReference>
   <bns:messageType>INVOIC</bns:messageType>
   <bns:messageReferenceNumber>1</bns:messageReferenceNumber>
   <bns:interchangeDate>250416</bns:interchangeDate>
   <bns:interchangeTime>1900</bns:interchangeTime>
   <bns:ackRequested/>
   <bns:outboundValidationStatus>N/A</bns:outboundValidationStatus>
   <bns:outboundValidationReport/>
   <bns:version>D</bns:version>
   <bns:release>96A</bns:release>
   <bns:controllingAgency>UN</bns:controllingAgency>
  </bns:result>

Supported operations​

SOAP implementation​

Supported operations

SOAP implementation