The service description is a work in progress, and without version control, as long as this note is here.

Service facts

• Name: PassengerEventSubmitService

• Operations, see Service operations. 

• REST based service. Operations are accessed using HTTPS POST.
• Service security: Decided by implementation.

• Standard return codes are described here: Service error response

Introduction

Overview

This service defines a set of operations to submit information about passenger events.

Implementation considerations

Any implementation of this service MUST use the XSD files provided here: XSDs

It is however up to the service provider which data elements to support.

Any service provider should make available documentation about the actual implementation, including:

• • the address of the service.
  • any limitations in the implementation.

Purpose of this service description

This service description has the following purpose:

• • • Describe of service in enough detail for a service provider to implement it.
    • Describe the service so that a client (of this service) developer can use it.
    • Make available the XSD files necessary to implement and use the service.
    • Make it possible for relevant people at airports, airlines, handlers and other aviation partners to understand the available functionality and then to decide if to implement/use it or not.

Intended readership

• • IT architects
  • Developers
  • Business architects
  • Interested parties in the aviation community

Service operations

Data entities

Avinor use cases

XSDs