smsCode missing in StopPoint API response


#1

Hi,
https://api.tfl.gov.uk/StopPoint/Mode/bus?page=1 doesn’t return the smsCode although it is present in the response sample. Is the smsCode really supposed to be in the response ?

If not, how can I get all the smsCodes for all bus stop points ?

Thank you


#2

As this is in the schema is should be in the response right? Can we get an update if this can be rectified?


#3

can someone kindly answer my question please ?

Thank you


#4

Hi @nakkore We are looking into making this change to the API but it does require some work from our dev team. Do you mind sharing what your use case is for a bulk return of SMS bus stop codes so we can understand what you’re aiming to achieve? Thank you!


#5

Hi,
my app is based on sms codes (other than stop name & indicator) to identify a bus stop. I’m currently using the legacy countdown api which allows using sms codes directly with no further calls unlike the unified api.
As I’d like to use the unified api to get the arrivals with one single api call either you:
provide an api which accepts sms codes as input (instead of just naptan codes)
or
provide me a way to build a mapping between sms codes and naptan codes.
Currently I’m using the legacy feeds to build the mapping but it would be great to use the unified api without relying on anything else.

Thank you


#6

Thanks @nakkore! Sounds interesting. We’re always keen to hear how developers are using our open data. We didn’t envisage SMS codes being used as bus stop identifiers - Naptans are industry standard identifiers and used by transport providers throughout the UK. Any reason why you decided to use SMS codes above Naptans in your app?


#7

Two main reasons.
Firstly sms codes are advertised on the bus stops, so it’s public information and in my opinion a short and effective way to uniquely identify a stop. I like to provide the user with the possibility to add a stop to the favourites using the sms code (among other possibilities) for example or I want to show the sms code in relevant screens( nearby stops, bus routes etc).

Secondly other cities use a similar identifier (usually 5 digits) and sometimes it’s the only way to identify stops. The business logic of the app and the user interface as well in my case take advantage using this common identifier.

So in short internally the app could use naptans but I want to keep this useful piece of information for the public.

Thank you