Validation data for e-tickets in public transport vehicles of Riga Traffic

Open data API in a single place

Provided by Rīgas satiksme

Get early access to Validation data for e-tickets in public transport vehicles of Riga Traffic API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Rīgas satiksme catalog

Country of origin

Latvia

Updated

2026.03.05 00:00

Created

2018.08.08

Available languages

English

Keywords

Validācijas, E-Talons, Maršruts, Sabiedriskais transports

Datasource

Official portal for European data link

Quality scoring

Dataset description

The files "ValidationData*.zip" contain e-ticket validation data for different time periods. Daily validations are stored in a separate txt file . Description of data fields: Ier_ID - current record ID in the database, Park - attraction of the involved public vehicle to the park/depot, TranspType - type of public transport involved, GarNr - the onboard number of the public vehicle involved, MarsrNos - the name of the route executed, TMarsruts - number of the completed route (with the encoding of the mode of transport), Direction - the direction of the completed route, ValidTalonaId - e-ticket validation identification number, Time - timestamp for validation

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service