Getting information on disrupted trips at a stop
                For a given stop, this endpoint returns all trips that both:
- Arrive at the stop on a specified time interval.
 - Are affected by PuT events.
 
Authentication phase
Before using the endpoint, you must run the authentication phase (→ Login).
After the authentication, a session opens and a valid session token persists until:
- The end of the session time-out, that is set through the parameter sessionTimeout (→ OptimaWSI configuration > OptimaAuth section).
 - An explicit Logout call (→ Logout).
 
Request
GET
                
https://<OPTIMA_HOST_IP_ADDRESS>:<PORT_NUMBER>/optima-put/disruption/stop/{public_stop_id}
                        The path parameter public_stop_id is required. It is a specific identifier of a stop.
Request parameters
| Parameter | Required | Description | 
|---|---|---|
| 
                                         format  | 
                                    
                                         NO  | 
                                    Response format. It can be bytes or text. The default is bytes.  | 
                                
| 
                                         timeStamp  | 
                                    
                                         NO  | 
                                    
                                         Reference timestamp. Starting time from which the arrival times are retrieved. The default is now.  | 
                                
| 
                                         timeInterval  | 
                                    
                                         NO  | 
                                    
                                         Reference time interval. Duration for which the arrival times are retrieved. The starting time is timeStamp. The ending time is timeStamp+timeInterval. The format is the ISO-8601 duration format PnDTnHnMn.nS. The default is PT15M (15 minutes). Example: PT20.345S, which corresponds to 20.345 seconds.  | 
                                
Request content-type
Not applicable.
Request body (payload)
Not applicable.
Response status
| HTTP status | Description | 
|---|---|
| 
                                         200 OK  | 
                                    
                                         Result of the processed request.  | 
                                
| 
                                         400 Bad request  | 
                                    
                                         Several conditions can be classified under this code. Generally, when the API has been called with wrong arguments.  | 
                                
Response content-type
If in the request:
- format=bytes, the format of the response is application/x-google-protobuf.
 - format=text, the format of the response is text/plain.
 
Response output
Text containing all information about the disrupted trips at the stop.
In case of a bad request, a text message is returned, explaining what has caused the problem.
Request
https://<OPTIMA_HOST_IP_ADDRESS>:<PORT_NUMBER>/optima-put/disruption/stop/express_6405?format=text&timeStamp=2016-05-26T00:00:00&timeInterval=PT24H0M
                        Response status
| HTTP status | Description | 
|---|---|
| 
                                         200 OK  | 
                                    
                                         The processing request has been accepted.  | 
                                
Response output
header {
  gtfs_real time_version: "1.0"
  incrementality: FULL_DATASET
  timestamp: 1464272973
}
entity {
  id: "1"
  trip_update {
    trip {
      trip_id: "915422"
      route_id: "371"
    }
    stop_time_update {
      stop_sequence: 3
      arrival {
        delay: 0
        time: 1464249958
      }
      stop_id: "express_6405"
    }
  }
}