Skip to content

Implement stopId and stopSequence to PIP Estimates endpoint#55

Open
Movs22 wants to merge 2 commits into
carrismetropolitana:v2from
Movs22:patch-1
Open

Implement stopId and stopSequence to PIP Estimates endpoint#55
Movs22 wants to merge 2 commits into
carrismetropolitana:v2from
Movs22:patch-1

Conversation

@Movs22
Copy link
Copy Markdown
Contributor

@Movs22 Movs22 commented Jan 30, 2026

(Re)Added the stopId and added stopSequence to the PIP estimates endpoint.
stopId was marked as deprecated, however, this property is useful on multi-stop requests as it makes it possible to identify the stop corresponding to a given estimate.

An example use case where these properties would come in handy is, for example, fetching all estimates for a given terminal and displaying all of the estimates on a single web page WHILST identifying the stop (P1, P2...) of each estimate.

This change is useful on multi-stop requests (i.e. if someone were to send a request to this endpoint with all stops for a given terminal) as it makes it possible to identify the corresponding stop for each estimate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant