ItemPath 3.0 introduces a major API overhaul, replacing the legacy backend with a newer platform foundation built to support the next generation of the product.

- New platform foundation:
ItemPath now runs on a modernized backend architecture that replaces the legacy API and lays the groundwork for future product improvements.

- Guided migration to the new platform:
Upgrading to 3.0.0.0 moves cloud deployments from the legacy Flask stack to the new backend architecture, including a managed database migration path and release-specific deployment checks.

- Smoother transition for existing integrations:
The new API layer preserves existing route patterns for key endpoints, which helps reduce disruption to existing integrations during the transition.

- Modernized authentication and account flows:
Core account features now run through the overhauled backend, including login, token refresh, logout, first-user setup, and password reset flows.

- Performance improvements for Data Push and Data Pull:
We’ve improved how Data Push and Data Pull tasks are processed behind the scenes, helping integrations run more efficiently and reducing slowdowns caused by overlapping or overloaded background jobs.

- Breaking change: standardized error response structure:
Error responses are now standardized around a top-level `detail` field. Customers who rely on specific JSON error keys from the legacy API should update their integrations to support the new structure.

{
  "detail": "Current Password is incorrect."
}

{
  "detail": "ItemPath has encountered an unexpected error. We've logged this issue, but feel free to reach out to support@itempath.com.",
  "error_id": "uuid-unhandled"
}

Compatibility note:
If your integration currently parses keys such as `message`, `error`, or other endpoint-specific error fields, it should be updated to read `detail` instead. For unexpected server failures, it should also tolerate the presence of `error_id` for support tracing.

ItemPath 3.0.0.1

Data Pull

• Improved manual rerun handling for duplicate Data Pull jobs.
• Improved Data Pull result handling so errors and queued results are shown more clearly in the UI.

Licensing

• Improved invalid license handling with clearer error messaging.
• Simplified the license update flow in the UI.

Orders / Transactions

• Improved transaction filtering and list performance.
• Improved handling of transaction fields such as handling unit and reason code.

Reporting

• Improved trend line editing and validation in dashboards and reports.
• Improved table sorting behavior.

PowerPick / Connections

• Improved PowerPick SQL connection behavior for more reliable query execution.
• Improved PowerPick SOAP connection recovery when cached connection metadata becomes stale.
• Cleared SOAP cache automatically when API and worker services start.

Tasks

• Improved bulk task deletion filtering and ordering behavior.