Simulator Crewlist
Summary
Retrieves the crewlist for a simulator event.
Request
Code snippet: URL
GET /COMMON_SIMULATOR_CREWLIST?forDate={forDate}
Parameters
Name | Type | Description | Required | Schema / Format |
---|---|---|---|---|
forDate | Query | The date of the simulator events, if not specified default to today | no |
xsd:date LHP|LCAG |
accessCode | Query |
Access code for retrieving the simulator crew list. The access code is provided inside of the complete reference link when retrieving a duty plan. The link (inclusive the access code) is static and may be reused in future sessions. |
yes |
xsd:string [0-9]{4}[-][0-9]{2}[-][0-9]{2}Z YYYY-MM-DDZ |
Responses
Code | Description | Content-Type | Schema |
---|---|---|---|
200 | Simulator crewlist was delivered successfully. |
application/json | → Simulator Crewlist Model |
403 | Access to the simulator crew list is forbidden (e.g. an invalid access code). No or wrong access code has been provided. | application/json | → Processing Errors Model |
503 |
iFCM not available or not responding in time / Backend system not available | application/json | → Processing Errors Model |
500 | Service replies with an error message, e.g. no simulator event on specified date. | application/json | → Processing Errors Model |
Simulator Crewlist
Code snippet: Payload
[
{
"forDate" → xsd:string
"simulator" → xsd:string
"shift"→ xsd:string
"errorMessage" → xsd:string
"ftNumber" → xsd:string
"errorReply" → xsd:boolean
"entries" → [
"crewFunction" → xsd:string
"simulatorFunction" → xsd:string
"simulatorActivity" → xsd:string
"crewName" → xsd:string
"staffIdentifier" → xsd:string
]
}
]
Name | Description | Required | Schema / Format |
---|---|---|---|
forDate |
the date of the simulator event |
yes |
xsd:string [0-9]{4}[-][0-9]{2}[-][0-9]{2}Z |
simulator |
Simulatortype | yes |
xsd:string [A-Z]{3} |
shift | Simulator shift number | yes |
xsd:string [0-9] |
errorMessage | Error message, if specified other fields are empty | No | xsd:string |
ftNumber | Concrete Simulator Number | No | xsd:string |
errorReply | whether the response is an error reply | yes |
xsd:boolean true|false |
entries[] |
yes | ||
entries[] → crewFunction |
Crew function, e.g. CP, FO |
yes |
xsd:string CP|FO |
entries[] → simulatorFunction |
Simulator function, e.g. CC, CP |
yes |
csd:string CC|CP|FO |
entries[] → simulatorActivity |
Simulator activity, e.g. CH, FC |
yes |
xsd:string CH|FC |
entries[] → crewName |
Crew Name ("..." if the crew member has not given the permission to display its personal information) | yes |
xsd:string [A-Za-z ]+|[.][.][.] |
entries[] → staffIdentifier |
Personal Kennziffer ("..." if the crew member has not given the permission to display its personal information) | yes |
xsd:string [0-9]{6}[A-Z]|[.][.][.] |
Note: the simulator crewlist is implemented as an array of crewlists. This is to support the unlikely case of multiple simulator events of a crew member on the same day. In this case the array contains the simulator crewlists of the simulator events in reverse chronological order, i.e. the first list corresponds to the last simulator event on that day.
Example
Request
Code snippet: Get request
GET /v1/flight_operations/crew_services/COMMON_SIMULATOR_CREWLIST?forDate=2019-08-07Z&accessCode=4711
Response
Code snippet: Json
[
{
"forDate": "2019-08-07",
"simulator": "346",
"shift": "3",
"entries": [
{
"crewFunction": "CP",
"simulatorFunction": "CP",
"simulatorActivity": "EI",
"crewName": "CAMERANESI, ALIDA",
"staffIdentifier": "123456A"
},
{
"crewFunction": "CP",
"simulatorFunction": "CP",
"simulatorActivity": "EI",
"crewName": "L, MALTE",
"staffIdentifier": ""
},
{
"crewFunction": "CP",
"simulatorFunction": "CC",
"simulatorActivity": "EI",
"crewName": "S, STEFAN",
"staffIdentifier": ""
},
{
"crewFunction": "SF",
"simulatorFunction": "SF",
"simulatorActivity": "EI",
"crewName": "T, SIGMUND",
"staffIdentifier": ""
}
],
"errorMessage": null,
"ftNumber": null,
"errorReply": false
}
]
Docs Navigation
- Lufthansa Open API
- Getting Started
- Public API Method Details
- Flight Schedules
- Reference Data
- Offers
- Operations
- Flight Schedules
- Flight Status
- Flight Status by Route
- Flight Status at Arrival Airport
- Flight Status at Departure Airport
- Flight Status Response
- Customer Flight Information
- Customer Flight Information at Arrival Airport
- Customer Flight Information by Route
- Customer Flight Information at Departure Airport
- Customer Flight Information Response
- Notifications
- cargo
- Partner API Method Details
- FlightOps/Crew API Method Details