Unit4 Developer Portal

Build & Develop with Unit4

Access to hundreds of APIs and more

Latest Updates

NEW

Accounting area endpoints

Two new APIs now available:

Financial Transactions API - Transaction tracking and reporting
Supplier CIS Details API - Compliance and supplier data

NEW

Sales, Common and Sys Admin areas endpoints

Bulk operation capabilities enhanced:

Batch Operations API - Orchestrate multi-step operations across ERPx
Sales Orders Batch - Bulk order processing
Attribute Relations Batch POST - Manage attribute relationships at scale

ERPx 254.0.17 / 261.0.3

Deprecation Notice

Five APIs are deprecated and will not be supported after March 1, 2028. Review the Deprecated endpoints reference and plan your migrations.

MULTI-TYPE DATA COVERAGE

All Data, One Platform

Unit4 Developer Portal is the single platform to find all your U4ERP Integrations and more.

Plan your integrations with confidence

API Roadmap: What’s coming next

The API Roadmap provides visibility into planned API additions, enhancements, and deprecations across ERPx releases. Align your integration planning with upcoming platform developments and avoid building on endpoints scheduled for retirement.

Key highlights:

Planned APIs by release cycle
Feature enhancements and breaking changes
Timeline for new capabilities across all domains
Early visibility to adapt your roadmap

Check the Roadmap regularly to stay aligned with platform evolution and make informed decisions about which APIs to prioritize in your integrations.

Understand timelines and plan migrations

Deprecation timeline: A structured approach

APIs are deprecated with advance notice and clear timelines. The Deprecation Timeline ensures you have sufficient time to migrate integrations to supported endpoints without service interruption.

Key highlights:

Deprecation announcements by ERPx version
Retirement dates and support windows
Reason for each deprecation (replaced by, consolidated, etc.)

Review the full Deprecated endpoints reference and identify integrations that require migration.

Deprecation Timeline: A Structured Approach

Multiple versions, clear upgrade paths

Versioning strategy: Backwards compatibility & evolution

ERPx follows a structured versioning approach that balances innovation with stability. APIs are versioned to maintain backwards compatibility while allowing the platform to evolve without breaking existing integrations.

Key highlights:

Semantic versioning across ERPx releases
Backwards-compatible enhancements in minor versions
Breaking changes reserved for major versions
Clear deprecation notices before removal

Plan your upgrade cycles around major releases and monitor deprecation schedules to ensure your integrations remain current and supported.

Versioning Strategy: Backwards Compatibility & Evolution

Guiding you from request to response

Documentation approach

We are committed to delivering documentation that is clear, accurate, and consistent. Each API comes with:

Well-defined endpoints and parameters
Example requests
Guidance on authentication, pagination, and error handling

We will continue to evolve and enhance the developers’ experience by:

Expanding the API catalog beyond the initial ten APIs
Adding deeper examples and best-practice implementation guides

This is only the beginning. The portal will evolve alongside our platform, and your feedback will help shape what comes next.