MVP One has recently switched from using the PublicAPI format to the ODataAPI format. This change was made to align with current OData standards and expectations. 

See below for further information on the two API types and how this switch will impact MVP One customers.  

 

Legacy Public APIs

This was MVP One's original API used for integration. This format will remain available to current customers, in order to support existing customer integrations.

However these APIs will not be available to new customers who begin their MVP One subscription in June 2026 or later. 

 

Key Information

• Accessed through URL paths such as /PublicAPI/v1 and /PublicAPI/v2 
• Built on an older OData based implementation 
• Provides access to core entities such as Work Orders, Assets, Locations, Parts, and Purchasing 
• Uses older field names and naming patterns 

 

 

MVP One OData APIs

This is the current and strategic API platform for MVP One integrations. This format has been designed to align with modern standards and provide the most value to MVP One customers. 

Please note that all new MVP One Odata enhancements will be added only for the ODataAPI format.

 

Advantages of OData APIs

• Built using current OData benchmarks
• Expanded field coverage and consistent naming 
• Optimized for analytics and reporting tools 

 

Key Information

• Accessed through URL paths such as /ODataApi/v1
• Legacy PublicAPI URLs do not automatically change to ODataAPI URLs. Migration requires updating request URLs and validating field mappings.