Register an alarm for a single arrival and departure at a stop, with a callback url to be requested when the alarm is fired.
<response> <version>2</version> <code>200</code> <currentTime>1318879898047</currentTime> <text>OK</text> <data class="entryWithReferences"> <references/> <entry class="registeredAlarm"> <alarmId>1_7deee53d-9eb5-4f6b-8623-8bff398fcd5b</alarmId> </entry> </data> </response>
We provide an arrival-departure alarm callback mechanism that allows you to register an alarm for an arrival or departure event and received a callback in the form of a GET request to a url you specify.
In order to specify an alarm for something like "5 minutes before a bus departs, we provide the alarmTimeOffset which specifies when the alarm should be fired relative to the actual arrival or departure event. A value of 60 indicates that the alarm should be fired 60 seconds before, while a value of -30 would be fired 30 seconds after.
A note about scheduled vs real-time arrivals and departures: You can register alarms for trips where we dont have any real-time data (aka a scheduled arrival and departure) and we will fire the alarm at the appropriate time. Things get a bit trickier when youve registered an alarm for a scheduled arrival and we suddenly have real-time for the trip after youve registered. In these situations, we will automatically link your alarm to the real-time arrival and departure.
The response is the alarm id. Note that if you include #ALARM_ID# anywhere in your callback url, we will automatically replace it with the id of the alarm being fired. This can be useful when you register multiple alarms and need to be able to distinguish between them.
Also see the cancel-alarm api method, which also accepts the alarm id as an argument.