YipiiYipii IoT Docs

API Changelog

Every addition, change and deprecation in the Yipii IoT API, newest first, with the date it shipped and what an existing integration has to do about it.

Share

Track all changes, new features, and breaking changes to the Yipii IoT APIs.

2026-02-22

IoT-BE API

New Features:

  • DTC_DETECTED alert type for OBD-II diagnostic trouble code notifications
  • Connectivity gate — tracks tracker online/offline state
  • Odometer polling at 2-hour intervals with OdometerEntry history
  • Asset photo upload and gallery (POST /api/{account}/asset/{id}/photo)
  • FOTA device ID support in tracker lookup and pre-registration
  • Account linking endpoint for Yipii Mobility bridge (POST /api/{account}/link-mobility)
  • Bidirectional asset, tracker, SIM, and user sync with Mobility platform
  • Telemetry sync pipeline (odometer, connectivity) to Mobility

Improvements:

  • AVL tracker endpoint batch loading and response caching for large fleets
  • Throttled high-frequency database writes (last login, activity log)
  • Fixed odometer race condition on concurrent updates
  • New Teltonika hardware models in device registry
  • Billing enforcement modes (warning, restricted, suspended)
  • Feature add-on purchases via Paddle webhooks

AI Service

New Features:

  • Fleet chat assistant (Yipster) with natural language fleet queries
  • Live fleet status tool — reads real-time vehicle positions from tracking map
  • Frozen/stuck asset diagnostic tool with device reset capability
  • Documentation search tool
  • Session persistence with chat history
  • Platform-aware tools for IoT and Mobility contexts

Reporting Service

Improvements:

  • PDF export handlers for all report types
  • Auto-detection of temperature data source (analog vs BLE beacon)
  • Cursor-based batching for large date ranges
  • Improved column ordering and default visibility

2026-02-01

IoT-BE API

New Features:

  • Public tracking links with multiple access modes (public, email, email_code, authorized_only)
  • Account-level branding settings (logo, primary color)
  • Account default contact details for tracking links
  • Route management for school transport tracking
  • API documentation portal at /docs

Improvements:

  • Enhanced asset location endpoint with additional IO data
  • Improved WebSocket connection stability

Reporting Service

New Features:

  • Mileage report types (monthly, weekly, daily)
  • Real-time report status via WebSocket at wss://ws-reporting.yipii.io
  • Report caching for faster repeated requests

Improvements:

  • Report generation performance improvements
  • Better error messages for validation failures

2026-01-15

IoT-BE API

New Features:

  • Beacon/tag creation endpoint (POST /api/{account}/tag)
  • Device reset command endpoint (POST /api/{account}/tracker/{id}/reset)
  • Command history view (GET /api/{account}/tracker/{id}/commands)
  • BLE toggle configuration (PUT /api/{account}/tracker/{id}/ble)
  • QR code scanner for tracker lookup

Improvements:

  • Billing API with subscription status and usage tracking
  • Enhanced tracker diagnostics endpoint

Reporting Service

New Features:

  • Dashboard endpoints migration from iot-be
  • Service degradation monitoring and health checks

2026-01-01

IoT-BE API

Improvements:

  • All DELETE operations now use native HTTP DELETE method
  • All PUT operations now use native HTTP PUT method
  • Improved error response consistency

Breaking Changes:

None in this release.


2025-12-15

IoT-BE API

New Features:

  • Asset grouping (/api/{account}/asset-group)
  • Service reminders (/api/{account}/service-reminder)
  • Renewal reminders (/api/{account}/renewal-reminder)
  • Fuel entry tracking (/api/{account}/fuel-entry)
  • Odometer entries (/api/{account}/odometer-entry)

Improvements:

  • Enhanced filtering on asset list endpoint
  • Pagination improvements with cursor-based option

2025-12-01

IoT-BE API

New Features:

  • Alert configuration API (/api/{account}/alert)
  • Alert type management
  • Email notification preferences

Reporting Service

Initial Release:

  • Trip reports
  • Activity reports
  • Stop reports
  • Multiple output formats (PDF, Excel, HTML, JSON)

Versioning Policy

The Yipii IoT API follows semantic versioning for major changes:

Change TypeImpactNotice Period
Major version (v1 to v2)Breaking changes, migration required90 days
Minor versionNew features, backward compatibleN/A
Patch versionBug fixes, no API changesN/A

Current API Version

The API does not currently use versioned URLs. All endpoints are available at:

https://api.yipii.io/api/{account_key}/

Breaking Change Policy

Breaking changes are announced at least 30 days in advance via:

  1. This changelog
  2. Email notification to API users
  3. Dashboard notification

Deprecation Process

When features are deprecated:

  1. Announcement: Feature marked as deprecated in docs
  2. Warning Period: 90 days with deprecation warnings in responses
  3. Removal: Feature removed after warning period

Subscribe to Updates

Stay informed about API changes:


Migration Guides

HTTP Method Changes (2026-01-01)

If you were using POST for DELETE or PUT operations, update your code:

Before:

// Old: POST with _method parameter
fetch(`${API_BASE}/asset/123`, {
  method: 'POST',
  body: JSON.stringify({ _method: 'DELETE' })
});

After:

// New: Native DELETE method
fetch(`${API_BASE}/asset/123`, {
  method: 'DELETE'
});

New access types for public tracking links:

Access TypeDescription
publicAnyone with the link can view
emailRequires email verification
email_codeRequires email + code verification
authorized_onlyRequires API authentication

Example:

const link = await fetch(`${API_BASE}/public-tracking-link`, {
  method: 'POST',
  headers,
  body: JSON.stringify({
    asset_id: 123,
    access_type: 'email_code',
    name: 'Secure Tracking Link'
  })
});

Was this page helpful?