Meat Messaging JSON data format for API upload

The required information for completing a consignment with Meat Messaging can be managed through JSON format payload and API upload.

Requirements of accurate and correct terminology for information to be uploaded to Meat Messaging

The information contained in Meat Messaging is used for the purpose of export trade of meat. This means the information entered into Meat Messaging must comply with Meat Notices related to product description.
For more details refer to Meat Notice:

• Meat Notice 2016-02 - Reminder of AUS-MEAT's responsibilities for accuracy of trade descriptions as they relate to export meat.
• Meat Notice 2021-02 Update - Electronic Meat Transfer Certificates (eMTC).
• Meat Notice 2021-03 - Alternate protocol for confirming illegible or missing shipping marks for packed products (meat) exported to USA.
• Meat Notice 2023-04 – Regulation of Shipping Marks – USA.

Payload Change Release Dates

• Jan 2014 - First release
• Jun 2019 - updates for additional trade description segments mm_det_IMD_E_A through to mm_det_IMD_E_F
• Aug 2019 - updates for Add QA segments - QA segments are used for 3rd party cold stores, TDT_20_email - Transport company email address, and mm_det_IMD_C_c - Corrected text description for segment
• Nov 2019 - updates for Destination management (LOC_8_dest_city and LOC_36_dest_country), and on the line level the Certificate of Analysis (mm_det_AAY_CFA )and Certificate of Origin (mm_det_AAY_COO)
• Mar 2021 - update for Receipt message through API and JSON payload. Add Status message through API and JSON Get request. Update to "BGM_function" option list to align with API model. Add "EX_MMCID" segment for NPE message access.
• May 2023 - update for Meat Messaging Industry Notice Meat Messaging Industry Notice changes that will come into force on the 1st of May 2024.
• Jun 2024 - update for "Required" segments now shown as 3 distinct values for Export messages, eMTCs and Domestic messages
• Jul 2024 - update for additional group level segments mm_det_PIA_GSIN (Global Shipment Identification Number) and mm_det_IMD_E_G (Handbook of Australian Meat distinct four-digit number)

Who uploads messages into Meat Messaging?

There are many different sections of the Meat Supply Chain that interact with Meat Messaging.

Interaction occurs from the Export Processing Establishment that produce cartons of meat all the way through to end users and retailers in export markets.

The Australian Export Establishments and Non-Packer Exporters (NPE)s generally are the creators of messages that are uploaded into Meat Messaging. The receivers or owners of shipments access the consignment information from meat messaging.

Detailed overview of who uses Meat Messaging: Who Uses Meat Messaging and Who Uploads Messages

GS1 Carton and Carcase Barcodes

Each case/carton, carcase, and bulk package is barcoded following the GS1 standards for Global Trade Item Number (specifically GTIN-14) and the Application Identifiers (AIs) for weight, date, and serial number. This ensures that each case/carton is barcoded with a global unique number that provides the basis for traceability along the whole supply chain. For more information on the GS1 standards go to: gs1.org

The barcodes used in Meat Messaging MUST be GS1 compliant barcodes.

Further information on case/carton labels can be found on the RMSCC site here: Case/Carton Labels (barcodes)

Further information on carcase tickets can be found on the RMSCC site here: Carcase Tickets (barcodes)

Mapping of Data Elements to eMTC PDF and Export Barcode Report

Mapping for eMTC PDF: Meat_Messaging_MTC_Field_Mapping.pdf

Example eMTC JSON payload: emtc_example.json

Mapping for Export Barcode Report: Meat_Messaging_Report_Field_Mapping.pdf

Understanding Message SSCC and group level SSCC usage

The Meat Messaging system is based on the use of the GS1 standards for trade and commerce. This includes the use of the GS1 Serial Shipping Container Code (SSCC). Refer to the GS1 standards for information of the construction of the SSCC. Within the Meat Message usage there is a Message Level SSCC that uniquely identifies the message as well as Group Level SSCCs that uniquely identify each group, virtual pallet or physical pallet. A Meat Messaging SSCC must never repeat.

Explanation of the Message identification hierarchy: Meat Messaging meat consignment identification hierarchy

Explanation of the SSCC usage: Meat Messaging Understanding SSCC usage

Meat Messaging GET Status returned JSON payload example

The purpose of the GET Status is to check the status of a message through GET using the SSCC.

API Swagger is available here: https://api.meatmessaging.info/swagger/ui/index#!/Message/Message_Status

• MessageStatus - Shows the status of the message with the options of 'OPEN', 'CANCELLED', 'SENT', 'RECEIPT'.
• RFF_AAK - Unique message reference of the last message uploaded to Meat Messaging.
• DateTimeCreated - System date time CCYYMMDDHHMM of the creation of the first message for the SSCC.

Validation Endpoint vs Process Endpoint

The Validation endpoint is used for validation the payload without committing data to the Meat Messaging database. This endpoint is used for testing during system development to ensure the payload is structurally valid. The Validation endpoint includes industry business rule validation and will return warnings and errors.

API Swagger is available here: https://api.meatmessaging.info/swagger/ui/index#!/Message/validate

The Process endpoint is used for uploading shipment details to Meat Messaging and the payload is committed to the Meat Messaging database. This endpoint is used for production.

API Swagger is available here: https://api.meatmessaging.info/swagger/ui/index#!/Message/process

Verification Endpoints

There are a number of Verification related endpoints. These end points are used for QA monitoring activities or for recording the details (including carton barcodes) on a verification of received product.

The SessionType needs to either be "QA" or "VALIDATION".

The Verification Create endpoint is available here: https://api.meatmessaging.info/swagger/ui/index#!/Message/Message_CreateMessageVerification

• MessageSSCC - The identifier of the message (shipment) that the verification is to be conducted.
• SessionType - Either "QA" for a QA monitoring Session or "VALIDATION" for a shipment verification session.
• MMUID - The MMUID of the person conducting the session.
• PreShipment - This is either 'true' or 'false' and is used for Pre or Post shipment message upload for QA monitoring.

After creation of a verification session a "SessionId" is returned. The "SessionId" is used for all further calls related to the verification session.

Other Verification endpoints include:

• GET /v1/message/verification https://api.meatmessaging.info/swagger/ui/index#!/Message/Message_GetMessageVerification
• POST /v1/message/verification/update https://api.meatmessaging.info/swagger/ui/index#!/Message/Message_UpdateMessageVerification
• POST /v1/message/verification/barcodes/add https://api.meatmessaging.info/swagger/ui/index#!/Message/Message_AddMessageVerificationBarcodes
• POST /v1/message/verification/finalise https://api.meatmessaging.info/swagger/ui/index#!/Message/Message_FinaliseMessageVerification

Meat Messaging Receipt JSON payload example

API Swagger is available here: https://api.meatmessaging.info/swagger/ui/index#!/Message/Message_Receipt

• Message_Source - Type of message and version of this type of message always set to the value MM-RECADV-22-01 until a new version of this message is released.
• MMCID - Receiving company/ company sending receipt message. The MMCID's corresponding "export establishment number" must match the "LOC_11_est" of the message being receipted, unless performing a self attestation, where the MMCID’s corresponding “export establishment number” must match the “DEQ_est_no” of the message being receipted. The MMCID in the payload must match the corresponding MMCID of the API Key used.
• MMUID - Meat Message User code for receiving officer. MMUID must be a member of the specified MMCID.
• RFF_AAK - Unique message reference of the company sending the receipt message.
• Message_SSCC - Message SSCC being the identification of the consignment being receipted.
• Received_DateTime - Date/Time of consignment receipt. Format: CCYYMMDDHHMM.
• Detailed_Inspection_Performed - If a detailed inspection has been conducted this value is 'true' else 'false'.
• Self_Attestation - If a Self Attestation has been conducted this value is 'true' else 'false'.
• Self_Attestation_Receiving_Officer - Name of receiving party officer if Self Attestation is performed.

Meat Messaging Cancel JSON payload example

Note: Cancellation is performed through the Process endpoint.

• Message_Source - Type of message and version of this type of message.
• MMCID - This is the Meat Messaging identification of the company. Must start with the number 1 and is 8 digits.
• RFF_AAK - Unique message reference of the company sending the cancel message. The RFF_AAK suffix letter MUST be imcremented
• BGM_type - This is set type of message with the options of 'Export', 'eMTC' or 'Domestic' .
• BGM_function - This is the flow control for the message with the value of 1 defining the message is to be Cancelled.
• Message_SSCC - Message SSCC being the identification of the consignment being cancelled.

API Swagger is available here: https://api.meatmessaging.info/swagger/ui/index#/

---

Meat Messaging DESADV JSON payload explanation

NOTE: Meat Messaging is an industry portal that holds the data uploaded by Export Establishments. The segment meaning and "Required" status for a number of segments change for the different message types of Export (Exp) message, eMTC (eMTC) and Domestic (Dom) message. The business rules and data validation for compliance to the Export Control Act and subordinate regulations and Meat Notices related to uploaded data is the responsibility of the uploading establishment. Meat Messaging does not control nor determine the business rules nor the validation requirements, these requirements are outlined by the Export Control Act and subordinate regulations and Meat Notices as interpreted by each uploading establishment. The number "1" indicates that the segment is required and "0" indicates that it is not mandatory, but is likely be required for certain market access, for commercial reasons or as determined by DAFF on a case by case basis.

segment_list.csv