Skip to main content
Eptura Knowledge Center

ManagerPlus API v2

  1. Last updated
  2. Save as PDF

An API (Application Programming Interface) connector is a tool that allows the application to share data with other business applications you may use, making it easier to get more done in one place.  This will allow you to gather data in a central location.  The data can be used to create reports, dashboards, and graphs in our Business Intelligence tool, giving you unprecedented insight into your business operations.

In order for connectors to work, they need to sync with Eptura Asset. That can be done by gathering the connectors database name, email address, password, and ensuring that you get a dedicated service account that is API enabled. After these items have been gathered, you will need to reach out to our technical support team who will help set up the connector for you.  

API changes now in effect with the release of API Version 2

For developers using the API, see the API V2 Documentation.

The following is a list of changes that will impact your ability to connect:

  • API keys will no longer be accepted in the query string (like `?api_key=...`). API keys must now be provided in the Authorization header (like `Authorization: ...`). This change prevents API keys from being saved in server logs—both our server logs and other Internet operators' logs.
  • Note that customers' existing API keys will continue to work.
  • The API URL is changing from `/api` to `/api2`.
Additional changes that don't cause breakage for customers or their API integrations:
  • Code and infrastructure have been updated and we expect to see performance improvements.
  • API documentation UI is different and it will provide the same information.
  • New endpoints have been added, including information about entities (sites), with more on the way.
  • The capitalization of some parameters has changed in the documentation, but all of those should be case insensitive. Old cases should still work. If they don't, it's a bug, though it's probably one of low priority.
  • Some API methods (mostly PATCH requests) now have different, improved error messages.
  • API keys can now be managed directly in the application and they are still available to manage in Classic.