StopPoint by Radius returns 400


I’m trying to access the StopPoint by Radius endpoint in Postman but have noticed that it’s returning some unexpected data.

The request is the following (my app_id and app_key have been omitted).

And the response has been

    "$type": "Tfl.Api.Presentation.Entities.ApiError, Tfl.Api.Presentation.Entities",
    "timestampUtc": "2020-07-26T08:16:52.4798949Z",
    "exceptionType": "ApiArgumentException",
    "httpStatusCode": 400,
    "httpStatus": "BadRequest",
    "relativeUri": "/Place?type=StopPoint&lat=51.494&lon=-0.100&radius=200&categories=",
    "message": "The following place type is not recognised: StopPoint"

Is there something I’m doing on my side that I need to fix or is there a server side issue at play here?

Thank you!

I think you are using the wrong call: StopPoint is not an entry in /Place/Meta/PlaceTypes (see below). Try using /StopPoint?radius

|28|“WaterfreightOther Access Point”|

@nickp Thanks for your response but I think there’s something else going on. This is happening with multiple endpoints across the whole system

This call

is returning

    "$type": "Tfl.Api.Presentation.Entities.ApiError, Tfl.Api.Presentation.Entities",
    "timestampUtc": "2020-07-26T12:32:37.770496Z",
    "exceptionType": "EntityNotFoundException",
    "httpStatusCode": 404,
    "httpStatus": "NotFound",
    "relativeUri": "/StopPoint?lat=51.494&lon=-0.100&stopTypes=NaptanMetroStation&includeDistances=false&radius=200&useStopPointHierarchy=true",
    "message": "Resource not found: http://api:8001/StopPoint?lat=51.494&lon=-0.100&stopTypes=NaptanMetroStation&includeDistances=false&radius=200&useStopPointHierarchy=true"

I’m guessing the documentation/Postman collection is out of date/being updated

After doing a little more searching it looks like this is the correct URL for what I was

Thanks to this post for getting me in to the right place.

Looks like the Postman collection and docs need updating but I’m guessing that’s coming :smiley: