Four ways to get Yipii data anywhere
Pick the approach that fits your team's tooling and engineering comfort.
REST API
Full programmatic access to fleet data. Create, read, and update records. Build custom integrations with internal systems.
Webhooks
Receive real-time event notifications. Fleet events trigger HTTP callbacks to your systems automatically.
Zapier
Connect Yipii to thousands of apps without code. Automate workflows between fleet data and business tools.
WhatsApp & messaging
Send fleet alerts and updates directly to WhatsApp and other channels. Keep teams informed where they work.
Full programmatic access to everything Yipii does
The Yipii REST API covers assets, trackers, alerts, trips, maintenance records, and more. API keys with scoped permissions. Public documentation at docs.yipii.io. Used by Yipii customers to integrate fleet data with internal systems, billing platforms, and custom dashboards.
- Read real-time and historical tracking data
- Manage work orders and maintenance records
- Access vehicle and asset profiles
- Configure alerts, geofences, and automations
- Authenticated via API keys with scoped permissions
- WebSocket live-tracking stream for real-time apps
Events pushed to you as they happen
Most fleet events fire webhooks: geofence entry/exit, speed threshold, temperature breach, device offline, work order completion, inspection results, document expiry. Retry logic and delivery tracking are built in. Use them to drive custom automation without polling.
- Real-time event delivery
- Retry logic with exponential backoff
- Full payload with asset and context
- Delivery tracking and failure visibility
No-code connections to thousands of apps
Yipii events flow into Zapier and out to 5000+ apps: Google Sheets for billing, Slack for team alerts, Salesforce for customer updates, QuickBooks for invoicing. For direct notifications, WhatsApp and email are native. SMS runs on a credit system.
- Zapier triggers for most Yipii events
- WhatsApp notifications for urgent alerts
- Email: free and unlimited
- SMS via credits (1 to 3 per message)
Frequently asked
Yes. A full REST API covers assets, trackers, alerts, trips, maintenance records, and more. Authentication is via API keys with scoped permissions. Documentation is public at docs.yipii.io.
Most fleet events: geofence entry/exit, speed threshold, temperature breach, device offline/online, work order status changes, inspection completion, document expiry, and more. Retry logic and delivery tracking are built in.
Yes, Zapier-ready workflows are available. Connect Yipii events to thousands of apps without writing code. Common use cases include syncing trip data to billing, pushing inspection outcomes to safety tools, and sending alerts to team messaging platforms.
Yes. A WebSocket live-tracking stream delivers position updates as they arrive from devices. This is the recommended approach for real-time dashboards and customer-facing tracking applications built on Yipii data.
A dedicated Reporting Service API handles trip and mileage data. This is optimised for aggregated queries across long date ranges and is separate from the main IoT-BE API that handles real-time operations.
API access is a paid add-on with flat monthly pricing. Webhooks are included in base plans. WhatsApp and SMS notifications consume credits (1 to 3 per message depending on destination). Email notifications are free and unlimited.