Overview

The operations in Airport Slot Data Service v2.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

InsertUpdateSlotSchedule (sequenceNumber: SequenceNumber, insertUpdateSlotScheduleInfo: InsertUpdateSlotScheduleInfo)

Insert a new slot schedule, or updates an existing one. 

Access method: POST

Parameters:

  • sequenceNumber: SequenceNumber 
    The sequenceNumber is incremented by 1 on each call to InsertUpdateSlotSchedule. If the has another value than expected the call should fail. The slot coordinator software should then use GetLastSequenceNumber to retrieve the last sequence number/transaction that was successfully processed, and restart from there. 


  • insertUpdateSlotScheduleInfo: InsertUpdateSlotScheduleInfo
    A Schedule pattern with corresponding information describing one or more arrivals or departures at one slot regulated airport that should be created or updated.

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.

DeleteSlotSchedule (sequenceNumber: SequenceNumber, deleteSlotScheduleInfo: DeleteSlotScheduleInfo)

Used to delete one or more flight schedules at a slot regulated airport. 

Access method: POST

Parameters: 

  • sequenceNumber : SequenceNumber
    The     sequenceNumber is incremented by 1 on each call to DeleteSlotSchedule. If the has another value than expected the call should fail. The slot coordinator software should then use GetLastSequenceNumber to retrieve the last sequence number/transaction that was successfully processed, and restart from there.

  • deleteSlotScheduleInfo : DeleteSlotScheduleInfo 
    A Schedule pattern describing one or more arrivals or departures at one slot regulated airport that should deleted. 

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.

GAInsertUpdateSlot (sequenceNumber: SequenceNumber, gaInsertUpdateSlotInfo: GAInsertUpdateSlotInfo)

Insert a new slot , or updates an existing one. 

Access method: POST

Parameters:

  • sequenceNumber: SequenceNumber 
    The sequenceNumber is incremented by 1 on each call to GAInsertUpdateSlot. If the has another value than expected the call should fail. The slot coordinator software should then use GetLastSequenceNumber to retrieve the last sequence number/transaction that was successfully processed, and restart from there. 


  • gaInsertUpdateSlotInfo: GAInsertUpdateSlotInfo
    Information about an arrival or departure slot at one slot regulated airport that should be created or updated.

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.

GADeleteSlot (sequenceNumber: SequenceNumber, deleteSlotInfo: GADeleteSlotInfo)

Used to delete one or flight slot at a slot regulated airport. 

Access method: POST

Parameters: 

  • sequenceNumber : SequenceNumber
    The     sequenceNumber is incremented by 1 on each call to GADeleteSlot. If the has another value than expected the call should fail. The slot coordinator software should then use GetLastSequenceNumber to retrieve the last sequence number/transaction that was successfully processed, and restart from there.

  • gaDeleteSlotInfo : GADeleteSlotInfo 
    Identifying one arrival or departure at one slot regulated airport that should deleted. 

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.

GetLastSequenceNumber(): SequenceNumberSet

Return the last sequence number successfully processed by the InsertUpdateSlotSchedule, DeleteSlotSchedule, GAInsertUpdateSlot and GADeleteSlot calls. 

Access method: GET

Parameters: None

Returns: The last sequence number(s) successfully processed.


Heartbeat (): void

The slot coordinator software call the heartbeat operation regularly to indicate that it is running ok, and that the connection is ok. The actual rate must be agreed upon between the slot coordinator and the airport.

Access method: POST

Parameters: None

Returns: Nothing

  • No labels