Overview

The operations in BRS Integration Service v 1.0 submits data that typically will be asynchronously processed. This means that all data that follow the syntax will be accepted, but it might not be used by downstream systems.

Service error response

If a service specific error occurs the entity below will be returned. Any service specific errors will be documented with the actual service implementation.
ErrorResponse is typically used with HTTP Response Code: 400 Bad Request

timestamp: TimestampUTC

Timestamp when the error was generated by the service.

A precise time for when something happened. Always UTC.

serviceErrorCode : ServiceErrorCode

An integer code representing a service specific error. The actual values are described in the service definition.

serviceErrorDescription: ServiceErrorDescription

A textual description of ServiceErrorCode.

Operations

SubmitBagEventData( BagEventDataIn )

Submits bag event data (BagEventData). This is data related to one bag, and with BagTagNumber as the key. The operation should be called for for all relevant bag events. See BagEventCode for a list of relevant events.

This operation is an extended version of the Baggage Information Exchange Service.SetBhsEventData operation.

Parameters

Returns

  • 200 OK if everything went well. The data is sent on for further processing.
  • 400 Bad Request if there were any issues with the input data. Service error response defies how to get more information about the actual problem.
  • Other error/warning returns are possible.

SubmitBatchEventData( BatchEventDataIn )

Submits batch event data (BatchEventData). 

Parameters

Returns

  • 200 OK if everything went well. The data is sent on for further processing.
  • 400 Bad Request if there were any issues with the input data. Service error response defies how to get more information about the actual problem.
  • Other error/warning returns are possible.

  • No labels