Warning: file_put_contents(/opt/downloads/cloud.meatmessaging.info/segment_list.csv): Failed to open stream: No such file or directory in /opt/sites/cloud.meatmessaging.org/json_api_format.php on line 58
Meat Messaging JSON data format for API upload

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 exporting and trading of meat. This means the information entered into Meat Messaging must comply with Meat Notices related to product description.

For more details refer to these Meat Notices:


Payload change release dates

Who uploads messages into Meat Messaging?

Many different sections of the meat supply chain interact with Meat Messaging.

Interactions take place all the way from the export processing establishments that produce cartons of meat through to end users and retailers in export markets.

Generally, Australian export establishments and non-packer exporters (NPEs) are the creators of messages uploaded into Meat Messaging. Consignment information is accessed from Meat Messaging by the receivers or owners of shipments.

Overview of who uses Meat Messaging: Who uses Meat Messaging and who uploads messages?

Detailed use cases: Use cases for export messages, eMTCs and domestic 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 globally 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 on the construction of the SSCC. Within Meat Messaging 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.

  {
       "MessageStatus":"OPEN",
       "RFF_AAK":"193388888840400001A",
       "DateTimeCreated":"202103181456",
   }

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


Validation endpoint vs process endpoint

The validation endpoint is used for validation of 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


Integration of QA monitoring - why do we need it?

QA monitoring exists in Meat Messaging to verify that the cartons physically loaded into a shipment are the same cartons that are recorded in the Meat Messaging consignment message. Its primary purpose is to provide assurance over product identity, traceability, and load-out accuracy.

Specifically, QA monitoring: