spider_sdk 1.3.1

Native Dart SDK for the Spider transit API — trip planning, stop search, and live realtime data.

spider_sdk (Dart / Flutter)

The Dart SDK for Spider — the managed transit API by Tiducto. Trip planning, stop search, and live realtime data behind one typed client that speaks the published API contract and attaches auth for you.

Native Dart package (single dependency: package:http), usable from Flutter (iOS/Android/web/desktop) and plain Dart. Sibling of the Kotlin, TypeScript, and Swift SDKs — same domain model, Dart idioms (Future, Stream, sealed classes).

Install

dependencies:
  spider_sdk: ^1.3.0

Quickstart

import 'package:spider_sdk/spider_sdk.dart';

final client = SpiderClient('https://your-env-slug.api.tiducto.eu', apiKey);

final result = await client.routing.plan(PlanOptions(
  origin: const Location.coordinate(49.19, 16.61),
  destination: const Location.coordinate(49.23, 16.53),
  departAt: DateTime.now(),  // leave now…
  searchWindowMinutes: 60,   // …and scan the next 60 minutes
));

switch (result) {
  case Success(:final value):
    for (final edge in value.edges) {
      final legs = edge.itinerary.legs.map((l) => l.mode?.name ?? 'walk').join(' → ');
      print('${edge.itinerary.durationSeconds ~/ 60} min: $legs');
    }
  case Failure(:final error):
    print('plan failed: ${error.code.name} — ${error.message}');
}

The recommended query pins a time and a window — a departure time (departAt) or an arrival deadline (arriveBy) together with searchWindowMinutes — rather than asking for N results from "now". Widen the window for sparse or intercity routes, and page through adjacent windows with planNext / planPrevious.

Ordinary failures are values — every call returns a SpiderResult<T> (Success / Failure) you branch on.

What's in it

• client.routing — trip planning (with paging and a streaming planStream), departures, and single-trip lookups.
• client.stops — text search, geo queries (nearest / bounding box), and lookup by GTFS id.
• client.realtime — poll-based live vehicle positions, delays, and alerts, plus change-detecting poll… streams (no push connections).

Full API reference and guides → docs.tiducto.eu. Product overview → tiducto.eu.

Contract & codegen

The routing wire models under lib/src/contract/ are generated from the published contract by scripts/generate-contract.sh (via tiducto/spider-codegen) and committed — the package carries the types, not the spec. Routing, stop and realtime calls go to the contract's /routing/v1, /stops/v1 and /realtime/v1 operations on your environment's host. client.contractVersion reports the contract version this SDK speaks. Don't hand-edit generated files; re-run the script.

License

Apache-2.0 — see LICENSE.