### Example Realtime Trains API JSON Response

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

A comprehensive example JSON payload demonstrating all possible fields that may appear in a Realtime Trains API output, providing a full structure without distinguishing between simple and detailed views.

```json
{
   "location": {
       "name": "Bournemouth",
       "crs": "BMH",
       "tiploc": "BOMO"
   },
   "filter": null,
   "services": [
       {
           "locationDetail": {
               "realtimeActivated": true,
               "tiploc": "BOMO",
               "crs": "BMH",
               "description": "Bournemouth",
               "wttBookedArrival": "011630",
               "wttBookedDeparture": "011830",
               "gbttBookedArrival": "0117",
               "gbttBookedDeparture": "0118",
               "origin": [
                   {
                       "tiploc": "WATRLMN",
                       "description": "London Waterloo",
                       "workingTime": "230500",
                       "publicTime": "2305"
                   }
               ],
               "destination": [
                   {
                       "tiploc": "POOLE",
                       "description": "Poole",
                       "workingTime": "013000",
                       "publicTime": "0130"
                   }
               ],
               "isCall": true,
               "isPublicCall": true,
               "realtimeArrival": "0114",
               "realtimeArrivalActual": false,
               "realtimeDeparture": "0118",
               "realtimeDepartureActual": false,
               "platform": "3",
               "platformConfirmed": false,
               "platformChanged": false,
               "displayAs": "CALL"
           },
           "serviceUid": "W90091",
           "runDate": "2013-06-11",
           "trainIdentity": "1B77",
           "runningIdentity": "1B77",
           "atocCode": "SW",
           "atocName": "South West Trains",
           "serviceType": "train",
           "isPassenger": true
       }
   ]
}
```

--------------------------------

### Example Realtime Train Service Data Output

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-service-information.md

This JSON snippet provides a complete example of the data returned for a single train service. It includes details such as service UIDs, dates, train identity, power type, ATOC codes, and an array of locations with their respective real-time and booked arrival/departure times, platform information, and status.

```json
{
    "serviceUid": "W72419",
    "runDate": "2013-06-11",
    "serviceType": "train",
    "isPassenger": true,
    "trainIdentity": "2A61",
    "powerType": "EMU",
    "trainClass": "B",
    "atocCode": "SN",
    "atocName": "Southern",
    "performanceMonitored": true,
    "origin": [
        {
            "tiploc": "BRGHTN",
            "description": "Brighton",
            "workingTime": "230500",
            "publicTime": "2305"
        }
    ],
    "destination": [
        {
            "tiploc": "VICTRIC",
            "description": "London Victoria",
            "workingTime": "003900",
            "publicTime": "0039"
        }
    ],
    "locations": [
        {
            "realtimeActivated": true,
            "tiploc": "BRGHTN",
            "crs": "BTN",
            "description": "Brighton",
            "wttBookedDeparture": "230500",
            "gbttBookedDeparture": "2305",
            "origin": [
                {
                    "tiploc": "BRGHTN",
                    "description": "Brighton",
                    "workingTime": "230500",
                    "publicTime": "2305"
                }
            ],
            "destination": [
                {
                    "tiploc": "VICTRIC",
                    "description": "London Victoria",
                    "workingTime": "003900",
                    "publicTime": "0039"
                }
            ],
            "isCall": true,
            "isPublicCall": true,
            "realtimeDeparture": "2304",
            "realtimeDepartureActual": true,
            "realtimeGbttDepartureLateness": null,
            "platform": "6",
            "platformConfirmed": true,
            "platformChanged": false,
            "line": "M",
            "lineConfirmed": true,
            "displayAs": "ORIGIN"
        },
        {
            "realtimeActivated": true,
            "tiploc": "ECROYDN",
            "crs": "ECR",
            "description": "East Croydon",
            "wttBookedArrival": "001700",
            "wttBookedDeparture": "001800",
            "gbttBookedArrival": "0017",
            "gbttBookedDeparture": "0018",
            "origin": [
                {
                    "tiploc": "BRGHTN",
                    "description": "Brighton",
                    "workingTime": "230500",
                    "publicTime": "2305"
                }
            ],
            "destination": [
                {
                    "tiploc": "VICTRIC",
                    "description": "London Victoria",
                    "workingTime": "003900",
                    "publicTime": "0039"
                }
            ],
            "isCall": true,
            "isPublicCall": true,
            "realtimeArrival": "0017",
            "realtimeArrivalActual": true,
            "realtimeDeparture": "0018",
            "realtimeDepartureActual": true,
            "platform": "4",
            "platformConfirmed": true,
            "platformChanged": false,
            "line": "S",
            "lineConfirmed": true,
            "displayAs": "CALL"
        },
        {
            "realtimeActivated": true,
            "tiploc": "CLPHMJC",
            "crs": "CLJ",
            "description": "Clapham Junction",
            "wttBookedArrival": "003100",
            "wttBookedDeparture": "003200",
            "gbttBookedArrival": "0031",
            "gbttBookedDeparture": "0032",
            "origin": [
                {
                    "tiploc": "BRGHTN",
                    "description": "Brighton",
                    "workingTime": "230500",
                    "publicTime": "2305"
                }
            ],
            "destination": [
                {
                    "tiploc": "VICTRIC",
                    "description": "London Victoria",
                    "workingTime": "003900",
                    "publicTime": "0039"
                }
            ],
            "isCall": true,
            "isPublicCall": true,
            "realtimeArrival": "0033",
            "realtimeArrivalActual": false,
            "realtimeDeparture": "0034",
            "realtimeDepartureActual": false,
            "platform": "14",
            "platformConfirmed": false,
            "platformChanged": false,
            "line": "SL",
            "lineConfirmed": false,
            "serviceLocation": "APPR_STAT",
            "displayAs": "CALL"
        },
        {
            "realtimeActivated": true,
            "tiploc": "VICTRIC",
            "crs": "VIC",
            "description": "London Victoria",
            "wttBookedArrival": "003900",
            "gbttBookedArrival": "0039",
            "origin": [
                {
                    "tiploc": "BRGHTN",
                    "description": "Brighton",
                    "workingTime": "230500",
                    "publicTime": "2305"
                }
            ],
            "destination": [
                {
                    "tiploc": "VICTRIC",
                    "description": "London Victoria",
                    "workingTime": "003900",
                    "publicTime": "0039"
                }
            ]
```

--------------------------------

### API Endpoints for Real-Time Train Information

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

Defines the various URL structures for querying real-time train departure and arrival information, including options for station, destination, date, and time filtering. Notes on appending '/arrivals' and parameter order are also included.

```APIDOC
Endpoints:
  Normal queries (live departures): /json/search/<station>
  Normal queries filtered to a location: /json/search/<station>/to/<toStation>
  Queries for all services on a specific date: /json/search/<station>/<year>/<month>/<day>
  Queries for services on a specific date and time: /json/search/<station>/<year>/<month>/<day>/<time>

Note:
  - You can append '/arrivals' to any of these endpoints to retrieve info about arrivals.
  - You can apply the to/from filtering to any of the endpoints, they must be before any date/time modifiers.
```

--------------------------------

### API Output Structure: Pair Object

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

Describes the 'Pair' object, used for origin and destination details within the API responses. It includes the TIPLOC, textual description of the location, and relevant working and public times for activities like departures or arrivals.

```APIDOC
Pair:
  tiploc: TIPLOC of the relevant location (example: WATRLMN)
  description: Text name of the relevant location (example: London Waterloo)
  workingTime: Relevant working time for this location for the activity that this pair is performing (format: HHmmss, example: 150330)
  publicTime: As workingTime but for the advertised public times (format: HHmm, example: 1503)
```

--------------------------------

### Realtime Trains API Field Descriptions

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

Detailed descriptions of various fields returned by the Realtime Trains API, including their purpose, data types, and possible values for understanding the structure of service data.

```APIDOC
cancelReasonCode:
  type: null
  description: If this service is cancelled at this location, this will be populated with a two character cancellation code which can be cross-referenced with the Delay Attribution Guide.
cancelReasonShortText:
  type: null
  description: Short text reason detailing the reason for the cancellation
cancelReasonLongText:
  type: null
  description: Long text reason detailing the reason for the cancellation
displayAs:
  type: -
  description: Values that can appear in this field are CALL, PASS, ORIGIN, DESTINATION, STARTS, TERMINATES, CANCELLED_CALL, CANCELLED_PASS. ORIGIN and DESTINATION represent the original origin & destination of a service. If STARTS or TERMINATES appear, then this means a service has started short or terminated en-route - the original origin/destination will show CANCELLED_CALL.
serviceLocation:
  type: null
  description: Values that can appear in this field are APPR_STAT (Approaching Station), APPR_PLAT (Arriving), AT_PLAT (At Platform, as referenced in platform), DEP_PREP (Preparing to depart) and DEP_READY (Ready to depart).
```

--------------------------------

### Realtime Trains API Field Definitions and Error Handling

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-service-information.md

Details the structure and possible values for key fields within the Realtime Trains API responses, along with common error conditions.

```APIDOC
cancelReasonCode:
  type: string | null
  description: If this service is cancelled at this location, this will be populated with a two character cancellation code which can be cross-referenced with the Delay Attribution Guide.
cancelReasonShortText:
  type: string | null
  description: Short text reason detailing the reason for the cancellation.
cancelReasonLongText:
  type: string | null
  description: Long text reason detailing the reason for the cancellation.
displayAs:
  type: string
  description: Values that can appear in this field are CALL, PASS, ORIGIN, DESTINATION, STARTS, TERMINATES, CANCELLED_CALL, CANCELLED_PASS. ORIGIN and DESTINATION represent the original origin & destination of a service. If STARTS or TERMINATES appear, then this means a service has started short or terminated en-route - the original origin/destination will show CANCELLED_CALL.
serviceLocation:
  type: string | null
  description: Values that can appear in this field are APPR_STAT (Approaching Station), APPR_PLAT (Arriving), AT_PLAT (At Platform, as referenced in platform), DEP_PREP (Preparing to depart) and DEP_READY (Ready to depart).

Errors:
  HTTP 404:
    description: Returned if the requested service cannot be found.
```

--------------------------------

### API Output: Pair Object Structure

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-service-information.md

Describes the structure of the 'Pair' object, which is used within the 'Service' object to represent origin and destination locations. It includes details such as TIPLOC, descriptive name, and relevant working and public times.

```APIDOC
Pair:
  tiploc: string - TIPLOC of the relevant location, example: WATRLMN
  description: string - Text name of the relevant location, example: London Waterloo
  workingTime: string (HHmmss) - Relevant working time for this location for the activity that this pair is performing. If it is in the context of an origin, it will be a departure time - for a destination it will be an arrival time.
  publicTime: string (HHmm) - As workingTime but for the advertised public times.
```

--------------------------------

### API Output Structure: Container Object

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

Describes the top-level 'Container' object returned by the API. It includes details about the location searched for, any applied filters, and an array of 'LocationContainer' objects containing service metadata.

```APIDOC
Container:
  location: LocationDetail object detailing the location searched for
  filter: LocationDetail objects detailing the location searched for, nested within from & to properties (default: null)
  services: Array of LocationContainer containing the location information and service metadata
```

--------------------------------

### Location Object Schema Definition

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

Defines the structure and properties of the 'Location' object used in the Realtime Trains API, including details about timetable information, real-time updates, and platform/line data.

```APIDOC
Location:
  realtimeActivated: boolean (default: false) - Details whether this service has been activated for realtime information
  tiploc: string (default: -) - TIPLOC code for the location, example: WATRLMN
  crs: string (default: null) - CRS code for the location, example: WAT
  description: string (default: -) - Text name of the relevant location, example: London Waterloo
  wttBookedArrival: string (format: HHmmss, default: null) - Working Timetable arrival time of the service at this location, in format HHmmss
  wttBookedDeparture: string (format: HHmmss, default: null) - Working Timetable departure time of the service at this location, in format HHmmss
  wttBookedPass: string (format: HHmmss, default: null) - Working Timetable passing time of the service at this location, in format HHmmss
  gbttBookedArrival: string (format: HHmm, default: null) - Public Timetable arrival time of the service at this location, in format HHmm
  gbttBookedDeparture: string (format: HHmm, default: null) - Public Timetable departure time of the service at this location, in format HHmm
  origin: Array<Pair> (default: -) - Array of Pair objects forming the origin of the service as at this location
  destination: Array<Pair> (default: -) - Array of Pair objects forming the destination of the service as at this location
  isCall: boolean (default: false) - boolean output as to whether this service calls at this location. This is set as true even if the service ends up non-stopping this station for whatever reason.
  isCallPublic: boolean (default: false) - boolean output as to whether this service makes a public call at this location. This is set as true even if the service ends up non-stopping this station for whatever reason.
  realtimeArrival: string (format: HHmm, default: null) - Expected or actual arrival time of this service, in format HHmm
  realtimeArrivalActual: boolean (default: false) - Always appears if realtimeArrival is also present. Boolean output stating whether this is an actual or expected time. If true, actual - if false, expected.
  realtimeArrivalNoReport: boolean (default: false) - If set as true, this means that the train has already arrived at this station but no report was received, and a later one has been
  realtimeWttArrivalLateness: number (default: 0) - If the service has an actual time, a lateness in minutes will be provided based from the WTT time. Positive values mean the service was late, negative values mean the service was early.
  realtimeGbttArrivalLateness: number (default: 0) - If the service has an actual time, a lateness in minutes will be provided based from the public timetable time. Positive values mean the service was late, negative values mean the service was early.
  realtimeDeparture: string (format: HHmm, default: null) - Expected or actual departure time of this service, in format HHmm
  realtimeDepartureActual: boolean (default: false) - Always appears if realtimeDeparture is also present. Boolean output stating whether this is an actual or expected time. If true, actual - if false, expected.
  realtimeDepartureNoReport: boolean (default: false) - If set as true, this means that the train has already departed this station but no report was received, and a later one has been
  realtimeWttDepartureLateness: number (default: 0) - If the service has an actual time, a lateness in minutes will be provided based from the WTT time. Positive values mean the service was late, negative values mean the service were early.
  realtimeGbttDepartureLateness: number (default: 0) - If the service has an actual time, a lateness in minutes will be provided based from the public timetable time. Positive values mean the service was late, negative values mean the service were early.
  realtimePass: string (format: HHmm, default: null) - Expected or actual passing time of this service, in format HHmm
  realtimePassActual: boolean (default: false) - Always appears if realtimePass is also present. Boolean output stating whether this is an actual or expected time. If true, actual - if false, expected.
  realtimePassNoReport: boolean (default: false) - If set as true, this means that the train has already passed this station but no report was received, and a later one has been
  platform: string (default: none) - The expected platform that this service will use at this location
  platformConfirmed: boolean (default: false) - boolean output - if this is set to true, then the service has used/will use the platform stated
  platformChanged: boolean (default: false) - boolean output - if this is set to true, then the service has changed from the planned platform
  line: string (default: none) - The expected line that this service will use at this location
  lineConfirmed: boolean (default: false) - boolean output - if this is set to true, then the service has used/will use the line stated
  path: string (default: none) - The expected path that this service will use at this location
  pathConfirmed: boolean (default: false) - boolean output - if this is set to true, then the service has used/will use the path stated
```

--------------------------------

### Realtime Trains API Error Responses

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

Information regarding error conditions and corresponding HTTP status codes returned by the Realtime Trains API, specifically for cases where a requested service cannot be found.

```APIDOC
Errors:
  HTTP 404:
    description: Returned if the requested service cannot be found.
```

--------------------------------

### API Output Structure: Location Container Object

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

Defines the 'LocationContainer' object, which holds detailed information about a specific location and its associated service metadata. This includes service identifiers, run dates, operator details, service type, and cancellation status.

```APIDOC
Location Container:
  locationDetail: Location object containing details about the location itself
  serviceUid: Service identifier for this service (regex pattern: [A-Z][0-9]{5})
  runDate: Running date of this service (format: YYYY-MM-DD)
  trainIdentity: The train identity that this service was planned to run to. FOC operated services will always show as FRGT.
  runningIdentity: Identifies the current running identity of the service.
  atocCode: The two character identifier, as used by ATOC, to identify the service operator (example: SW) (default: ZZ)
  atocName: Service operator (example: South West Trains) (default: Unknown)
  serviceType: Contains the type of service this is (bus, ship or train).
  isPassenger: Boolean output determining whether the service is a passenger service or not
  plannedCancel: Boolean output determining whether this service was a planned cancellation (default: false)
  origin: Array of Pair objects forming the overall origins of the service (only appears if en-route cancellation)
  destination: Array of Pair objects forming the overall destinations of the service (only appears if en-route cancellation)
  countdownMinutes: Number of minutes until expected departures (currently present only on 'high frequency' metro services)
```

--------------------------------

### Partial Realtime Train Journey Segment

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-service-information.md

This JSON fragment showcases a segment of a train's journey data from the Realtime Trains API. It includes details such as destination (tiploc, description, working and public times), various boolean flags for call types, real-time arrival data, platform number, and display preferences. Note that this is a partial object, likely nested within a larger train schedule response.

```json
                    "publicTime": "2305"
                }
            ],
            "destination": [
                {
                    "tiploc": "VICTRIC",
                    "description": "London Victoria",
                    "workingTime": "003900",
                    "publicTime": "0039"
                }
            ],
            "isCall": true,
            "isPublicCall": true,
            "realtimeArrival": "0041",
            "realtimeArrivalActual": false,
            "platform": "15",
            "platformConfirmed": false,
            "platformChanged": false,
            "displayAs": "DESTINATION"
        }
    ],
    "realtimeActivated": true,
    "runningIdentity": "2A61"
}
```

--------------------------------

### API Request Parameters

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-location-line-up.md

Details the required and optional parameters used across the Real-Time Trains API endpoints. This includes station identifiers (CRS or TIPLOC), and specific formats for date (yyyy/mm/dd) and time (hhmm).

```APIDOC
Parameters:
  station (required): CRS or TIPLOC
  toStation (optional): CRS or TIPLOC
  date (optional): In format yyyy/mm/dd, example: 2013/06/14
  time (optional): In format hhmm, example: 0810 or 2315
```

--------------------------------

### API Endpoint for Service Information Retrieval

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-service-information.md

Defines the URL structure for accessing specific service information. The endpoint requires a unique service identifier and a specific date to retrieve details about a train service.

```APIDOC
Endpoint: /json/service/<serviceUid>/<year>/<month>/<day>
```

--------------------------------

### Location Object API Reference

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-service-information.md

Defines the structure and properties of the 'Location' object returned by the Realtime Trains API. This object provides detailed information about a specific location (station) in the context of a train service, including scheduled and real-time arrival/departure/passing times, platform information, and service status.

```APIDOC
Location:
  realtimeActivated: boolean (default: false) - Details whether this service has been activated for realtime information
  tiploc: string - TIPLOC code for the location, example: WATRLMN
  crs: string | null (default: null) - CRS code for the location, example: WAT
  description: string - Text name of the relevant location, example: London Waterloo
  wttBookedArrival: string | null (format: HHmmss, default: null) - Working Timetable arrival time of the service at this location
  wttBookedDeparture: string | null (format: HHmmss, default: null) - Working Timetable departure time of the service at this location
  wttBookedPass: string | null (format: HHmmss, default: null) - Working Timetable passing time of the service at this location
  gbttBookedArrival: string | null (format: HHmm, default: null) - Public Timetable arrival time of the service at this location
  gbttBookedDeparture: string | null (format: HHmm, default: null) - Public Timetable departure time of the service at this location
  origin: Array<Pair> - Array of Pair objects forming the origin of the service as at this location
  destination: Array<Pair> - Array of Pair objects forming the destination of the service as at this location
  isCall: boolean (default: false) - Boolean output as to whether this service calls at this location. True even if non-stopping.
  isCallPublic: boolean (default: false) - Boolean output as to whether this service makes a public call at this location. True even if non-stopping.
  realtimeArrival: string | null (format: HHmm, default: null) - Expected or actual arrival time of this service
  realtimeArrivalActual: boolean (default: false) - Boolean stating whether realtimeArrival is actual (true) or expected (false)
  realtimeArrivalNoReport: boolean (default: false) - If true, train arrived but no report received, and a later one has been
  realtimeWttArrivalLateness: number (default: 0) - Lateness in minutes from WTT time if actual time is present (positive: late, negative: early)
  realtimeGbttArrivalLateness: number (default: 0) - Lateness in minutes from public timetable time if actual time is present (positive: late, negative: early)
  realtimeDeparture: string | null (format: HHmm, default: null) - Expected or actual departure time of this service
  realtimeDepartureActual: boolean (default: false) - Boolean stating whether realtimeDeparture is actual (true) or expected (false)
  realtimeDepartureNoReport: boolean (default: false) - If true, train departed but no report received, and a later one has been
  realtimeWttDepartureLateness: number (default: 0) - Lateness in minutes from WTT time if actual time is present (positive: late, negative: early)
  realtimeGbttDepartureLateness: number (default: 0) - Lateness in minutes from public timetable time if actual time is present (positive: late, negative: early)
  realtimePass: string | null (format: HHmm, default: null) - Expected or actual passing time of this service
  realtimePassActual: boolean (default: false) - Boolean stating whether realtimePass is actual (true) or expected (false)
  realtimePassNoReport: boolean (default: false) - If true, train passed but no report received, and a later one has been
  platform: string (default: none) - The expected platform that this service will use at this location
  platformConfirmed: boolean (default: false) - If true, service has used/will use the stated platform
  platformChanged: boolean (default: false) - If true, service has changed from the planned platform
  line: string (default: none) - The expected line that this service will use at this location
  lineConfirmed: boolean (default: false) - If true, service has used/will use the stated line
  path: string (default: none) - The expected path that this service will use at this location
  pathConfirmed: boolean (default: false) - If true, service has used/will use the stated path
```

--------------------------------

### API Parameters for Service Information Endpoint

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-service-information.md

Describes the mandatory parameters required when making a request to the service information API endpoint. These parameters are crucial for identifying the specific service and date for which information is requested.

```APIDOC
Parameters:
  serviceUid (required): Service UID, as obtained from a location search
  date (required): In format yyyy/mm/dd, example: 2013/06/14
```

--------------------------------

### API Output: Service Object Structure

Source: https://github.com/rorydotgg/realtime-trains-api-docs/blob/main/pull-service-information.md

Details the comprehensive structure of the 'Service' object returned by the API. This object contains extensive information about a train service, including its unique identifier, run date, type, identity, operator details, and arrays of associated locations, origins, and destinations.

```APIDOC
Service:
  serviceUid: string (regex: [A-Z][0-9]{5}) - Contains the service identifier for this service, paired with the run date this will always be a unique identifier.
  runDate: string (YYYY-MM-DD) - Contains the running date of this service, based on its departure time from the first origin.
  serviceType: string - Contains the type of service this is, bus, ship or train.
  isPassenger: boolean - boolean output determining whether the service is a passenger service or not
  trainIdentity: string - The train identity that this service was planned to run to. FOC operated services will always show as FRGT.
  powerType: string - The power type of the service. This is as described in the Network Rail CIF documentation.
  trainClass: string | null - The classes that this service conveys. If the field is blank and is a passenger train, the train conveys first and standard class accommodation only.
  sleeper: string | null - The types of sleeper that this service conveys.
  atocCode: string (default: ZZ) - The two character identifier, as used by ATOC, to identify the service operator, example: SW
  atocName: string (default: Unknown) - Service operator, example: South West Trains
  performanceMonitored: boolean - boolean output detailing whether the service is subject to PPM (Public Performance Measurement) monitoring.
  origin: Array<Pair> - Array of Pair objects forming the overall origins of the service, detailed further down.
  destination: Array<Pair> - Array of Pair objects forming the overall destination of the service, detailed further down.
  locations: Array<Location> - Array of Location objects forming the locations that the service calls at (and, in detailed, passes).
  realtimeActivated: boolean (default: false) - Details whether this service has been activated for realtime information
  runningIdentity: string - This field appears if realtimeActivated is set as true. It identifies the current running identity of the service.
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.