Connector details
Use explicit adapters, not hidden plugin behavior.
This page gives integrators a compact map of connector areas, current support, and where to read implementation details before using real data.
Connector Areas
| Area | Current support | Boundary | Docs |
|---|---|---|---|
| Telemetry | CSV replay, polling, webhook sidecar, JSON transform, authenticated POST. | Real credentials and payloads stay private. | Catalog |
| Prediction | Deterministic predictor and external HTTP adapter boundary. | Trip Updates remain pluggable and fail closed. | Prediction lab |
| Validation | Allowlisted GTFS and GTFS Realtime validator wrappers. | Browser requests do not supply commands or arbitrary paths. | Validation triage |
| Monitoring | Local helper and private summaries. | No hosted monitoring or SLA promise. | Operator smoke |
| Discovery | /public/feeds.json and public feed metadata. | No consumer submission or listing action. | Readiness |
Safe Integration Sequence
- Pick the closest current pathChoose telemetry, prediction, validation, monitoring, or discovery.
- Run synthetic checksUse committed fixtures and offline conformance before handling private data.
- Document failure behaviorMake fail-closed behavior, redaction rules, and owner responsibilities explicit.
- Configure real data privatelyUse deployment-owned secrets and keep private payloads out of public docs and screenshots.
- Return to feed reviewCheck how the integration changes Vehicle Positions, Trip Updates, Alerts, and readiness.
Limits
Connector details guide implementation. They do not prove named vendor compatibility, hardware certification, real-world fleet reliability, production readiness, consumer acceptance, SLA coverage, or ETA quality.