This article provides information on how to update Legacy APIs in MVP One.

  • May 12, 2026
  • Article

Title
MVP Version 1 and 2 Legacy APIs

Content

As a note, these APIs are considered Legacy APIs that will be deprecated. All future development should be done using MVP One's new API system.

API Access and Licensing

API access is controlled via a license structure. Please note that the daily API license will reset every day at midnight CST for all customers regardless of their time zone.

Customers inquiring about getting API access will need to contact their Account Executive. If you do not know how to contact your Account Executive, please contact MVP Technical Support (Support@MVPOne.com).

API URL Format

MVP API calls use a variety of URL schemes.
The MVP APIs use URLs formatted as such: https://CUSTOMERNAME.mvpplant.com/PublicAPI/v1/
The Customer Name is the prefix of your MVP site address. As an example. If you are using example.mvpplant.com, then your Customer Name is example.
 
 
 
Datetime Format
V1 URLs should use a datetime format of "DateTime'2025-05-02T00:00:00.000"
V2 URLs should use a datetime format of "2025-05-02T00:00:00.000Z"

 

OData API Header

Only specific headers are acceptable for Exporting or Importing with MVP API calls.

The following are acceptable headers for Exporting:

  1. Text/json
  2. Text/XML
The following are acceptable headers for Importing:
  1. Content-Type: Text/json
  2. Content-Type: Text/XML

 

 

API Metadata Feed

You can use the following URLs to view metadata feeds for our V1 and V2 APIs.

https://EnterCustomerNameHere.mvpplant.com/PublicAPI/v1/$metadata

https://EnterCustomerNameHere.mvpplant.com/PublicAPI/v2/$metadata

https://EnterCustomerNameHere.mvpplant.com/PublicAPI/v2/Reporting/$metadata

Metadata feeds can be used by tools like Visual Studio to automate development.

API GET DateTime Values

The datetime value in the GET URL should be in UTC. The time values returned in the results will match the user's time zone used to authenticate the GET request.

API Entity Names

When using API to access MVP data, all entity names are case-sensitive. Using all upper or lower case will result in errors.

API Record Cap

MVP's APIs will pull the first 2,000 records. If the limit is being reached. We recommend using the "$filter" option, to specify the data required to be pulled.

API Call Limit

Depending on your site's license, a certain number of API calls are allowed. This amount resets every 24 hours, resetting at 12 am Central Time. You can check your daily API usage and limit under Administration > Licenses.

 

Using OData 2.0 with MVP APIs?

Our OData APIs use OData 3.0. If using 2.0, the OData request must include a header specifying the "DataServiceVersion" of 2.0.

Using a Third Party API Program?

When customers use MVP APIs in conjunction with third-party programs, our Support Team may not be able to assist if the problem resides outside of MVP. In these cases, we will need to direct customers to contact the admin of their third-party API accessing programs.

API Filter Not Working in Java?

Spaces need to be encoded in the filter part of the URL.

  1. Replacing the spaces with either %20 or + fixes the issue.
  2. Here is the line of code from my example:URL url = new URL("https://tryitout.mvpplant.com/publicapi/v1/Accounts?$filter=CreatedBy%20eq%20'thorpk'");
  3. URL url = new URL("https://tryitout.mvpplant.com/publicapi/v1/Accounts?$filter=CreatedBy+eq+'thorpk'");
  4. Link to the examplehttp://rextester.com/QQQRBP1458

APIs Not Refreshing in PowerBi?

As a note, PowerBI will now allow the MVP One API Key authentication to refresh data into PowerBi.

 

 

URL Name
MVP-APIs
Administration