The Objective Measurement Metadata data specification outlines the elements and the structure of a JSON payload for reporting Objective Measurement usage.
The Objective Measurement Metadata data is intended to be used for industry program reporting and AUS-MEAT industry reporting and audit purposes.
The Objective Measurement Metadata payload is required to be create by a processing plant’s integrated system as there are many elements that are only available withing the plant’s systems.
One Objective Measurement Metadata payload needs to be created for each kill lot.
Data submitted to the Objective Measurement Metadata service directly utilises
HTTPSJSONRESTWeb APIs.
When data is submitted to the endpoint it is transported using the application/json encoding as a raw HTTP request. Responses from the Web API in turn will reply in the documented format using the application/json encoding.
All requests must be authenticated using an API Key as provided by Meat Standards Australia. The API Key is to be included as described in the Authorization header of the HTTP request.
REST APIs are described using OpenAPI Specification Version 3. The specifications may be used in-place, as static documentation, or used to generate client libraries using a variety of available tools.
When implementing HTTPS JSON REST, keys and values are case sensitive. A request may also contain additional properties that may be ignored. A response also may include additional properties which must be accepted and may be ignored.
(1) Please note, a relevant Meat Standards Australia (MSA) account is required to gain access to the developer documentation. Upon request, MSA will also issue an API key - this will be used for authentication and to gain access to the sandbox environments.
Details
Segment : Example
Format
Usage
Use Case
Purpose
Show
{
"rmsccMessageType":
{
Array
Mandatory
Identifies a group of elements related to the type of message payload
Identifier of a suitability trained an qualified person. Preferred ID is via AUS-MEAT number, if no AUS-MEAT number exists, a suitably unique processor identifier should be used. If there is no Human operator use code:
Identifier of a suitability trained an qualified person. Preferred ID is via AUS-MEAT number, if no AUS-MEAT number exists, a suitably unique processor identifier should be used. If there is no Human operator use code:
Identifier of a suitability trained an qualified person. Preferred ID is via AUS-MEAT number, if no AUS-MEAT number exists, a suitably unique processor identifier should be used. If there is no Human operator use code:
Identifier of a suitability trained an qualified person. Preferred ID is via AUS-MEAT number, if no AUS-MEAT number exists, a suitably unique processor identifier should be used. If there is no Human operator use code: