Integrations
Connect transport data with the services that support the journey.
WayWink works with mapping, communication, device and API capabilities to bring location, transport activity and user communication into connected school transportation workflows.
Connected transport
Integrations should support the workflow, not become another system to manage.
School transportation depends on information from more than one source. Location data may come from a device, mapping services provide geographic context, and communication services help information reach users.
WayWink brings those capabilities into the transport workflow so they can support routes, trips, vehicles, students, drivers and authorized families.
Integration scope can vary between deployments. We therefore distinguish between capabilities WayWink supports today and external systems that may require technical review before they can be connected.
Integration areas
Services around the transport journey.
WayWink uses a combination of external services and platform capabilities to support live transportation and communication.
Mapping & route context
Google Maps
WayWink uses mapping services to support route visualization, location context and transportation journeys.
Outbound communication
SMS
SMS can support transport communication where important information needs to reach users outside the application experience.
App notifications
Push notifications
Push notifications help surface journey updates and other transport information through supported mobile experiences.
Location & operational data
Device hardware
Supported device hardware can provide the location or transport data required by connected WayWink workflows.
System connectivity
APIs
API capabilities provide a foundation for exchanging supported information between WayWink and external systems.
Transport communication
Messaging
Messaging capabilities help schools communicate relevant transportation information within connected workflows.
How information moves
Turn incoming signals into useful transport context.
01
Device & location data
Supported devices provide operational signals such as location information.
02
WayWink transport context
WayWink connects incoming information with routes, vehicles, trips, stops and users.
03
Useful output
Journey information can then appear through dashboards, mobile apps, alerts and supported communication channels.
Maps & location
Give vehicle location geographic context.
Mapping helps WayWink present routes, stops and active vehicle location in a form that school teams, drivers and authorized families can understand.
Location and ETA accuracy can vary with device availability, positioning accuracy, network connectivity and road conditions.
Route context
Next stop · 8 min
Live vehicle position
Communication channels
Send transport information through the right channel.
Not every transport event belongs in the same place. WayWink can use different communication mechanisms depending on the user and the operational workflow.
Push notifications
Surface relevant updates inside supported mobile experiences.
SMS
Support transport communication through mobile text messaging where configured.
Messaging
Provide communication within supported WayWink transport workflows.
Operational alerts
WayWink can surface internal events such as SOS and other important transport signals.
Device connectivity
Connect supported hardware to the transport workflow.
Device hardware can provide operational data such as vehicle location. WayWink uses that information together with the active trip, vehicle and route context.
Hardware compatibility and deployment requirements should be reviewed for each implementation.
Device
Location data
WayWink
Transport context
Users
Useful visibility
API connectivity
A foundation for supported system connections.
APIs can support structured information exchange where a school or deployment needs another system to work with WayWink.
API availability, endpoints, authentication and data scope depend on the implementation. This page does not imply universal compatibility with every third-party system.
Built into WayWink
Some transport alerts are part of the platform itself.
SOS and transport event awareness should not be confused with third-party integrations. These are WayWink operational capabilities that can then use supported notification channels to reach the appropriate users.
Transport event
Driver SOS raised
Route 08 · Bus 12 · Active journey
School
Alert context
Notification
Supported channel
Users
Authorized view
Deployment considerations
Integration scope depends on the school's requirements.
We review external systems, devices and data requirements as part of the implementation rather than claiming automatic compatibility with every platform.
Integration availability can depend on deployment requirements.
External services may have their own availability, usage limits and terms.
Device connectivity depends on supported hardware and network conditions.
API access and scope depend on the agreed implementation.
Not every external school system is automatically supported.
Tell us what your transport environment needs to connect.
We can review your mapping, device, communication and system requirements and explain which WayWink integration options apply to your deployment.
Discuss integrations