db-vendo-client

The trip() method returns an object containing trip details, including line information, current location, origin, destination, and stopovers.

Key Timing Behavior: Following the Friendly Public Transport Format v2 draft spec, the returned departure and arrival times include the current delay. The departureDelay and arrivalDelay fields express the difference between the actual time and the scheduled time.

Note on realtimeDataUpdatedAt: This field is currently returned but not populated in db-vendo-client because the upstream APIs do not provide it.

{
	id: '1|31431|28|86|17122017',
	direction: 'S Spandau',
	line: {
		type: 'line',
		id: '18299',
		fahrtNr: '12345',
		name: 'S9',
		// ...
	},
	currentLocation: {
		type: 'location',
		latitude: 52.447455,
		longitude: 13.522464,
	},
	origin: {
		type: 'station',
		id: '900000260005',
		name: 'S Flughafen Berlin-Schönefeld',
		// ...
	},
	departure: '2017-12-17T18:37:00+01:00',
	plannedDeparture: '2017-12-17T18:37:00+01:00',
	departureDelay: null,
	// ...
	destination: {
		type: 'station',
		id: '900000029101',
		name: 'S Spandau',
		// ...
	},
	arrival: '2017-12-17T19:50:30+01:00',
	plannedArrival: '2017-12-17T19:49:00+01:00',
	arrivalDelay: 90,
	// ...
	stopovers: [ /* … */ ]
}

The client supports multiple profiles, each wrapping different DB APIs with varying capabilities, stability, and quota limits. Choose the profile that best fits your requirements for features like tickets, polylines, or API key usage.

The journeys() method resolves to an object containing:

• journeys: An array of journey objects. Each journey contains legs (the individual segments of the trip).
• earlierRef / laterRef: Tokens used for pagination.
• realtimeDataUpdatedAt: Timestamp of the last realtime update (currently not set in db-vendo-client).

Journey Leg Details

Each leg includes:

• tripId: Unique identifier for the trip.
• line: Information about the transport line (type, name, operator, etc.).
• origin / destination: Station details.
• departure / arrival: ISO strings including current delay.
• plannedDeparture / plannedArrival: Scheduled times.
• departureDelay / arrivalDelay: Difference between scheduled and actual time in seconds.
• remarks: Hints or warnings (e.g., barrier-free).

Note: If a leg is cancelled, cancelled: true is added, and time/platform fields will be null.

To obtain API dumps from the DB Navigator app, you must modify the Android application to allow user-installed Certificate Authorities (CAs) for SSL/TLS interception. This process involves decompiling the APK, modifying the network security configuration, and reinstalling the modified app on an Android device.

Steps to intercept traffic:

1. Download or extract the Split APK.
2. Merge the APK (e.g., using APKEditor).
3. Decompile the merged APK using apktool.
4. Edit res/xml/network_security_config.xml to allow user CAs (not just in debug mode).
5. Recompile the APK using apktool and sign it.
6. Install the signed APK on an Android device.
7. Intercept traffic using a MITM (Man-in-the-Middle) decryption tool. For example, use PCAPdroid with the mitm addon, which does not require root, by installing the CA certificate into the Android system store.

You can intercept and process raw Fetch Request and Response objects by providing logRequest and logResponse functions in the profile object passed to createClient.

• logRequest(ctx, fetchRequest, requestId): ctx contains the profile and options; fetchRequest is the Request object.
• logResponse(ctx, fetchResponse, body, requestId): fetchResponse is the Response object; body is the response body.

import {createClient} from 'db-vendo-client'
import {profile as dbProfile} from 'db-vendo-client/p/db/index.js'

const userAgent = 'link-to-your-project-or-email'

const logRequest = (ctx, fetchRequest, requestId) => {
	const {dbProfile, opt} = ctx
	console.debug(requestId, fetchRequest.headers, fetchRequest.body + '')
}

const logResponse = (ctx, fetchResponse, body, requestId) => {
	console.debug(requestId, fetchResponse.headers, body + '')
}

const client = createClient({
	...dbProfile,
	logRequest,
	logResponse,
}, userAgent)