5 results found
-
Add API Endpoint to update the security role on the end user
Currently, can add the User and Sites; however, CANNOT add security roles. Extremely time consuming to add security role on all Sites for Enterprise clients. API development requested.
2 votesThank you for your suggestion—this idea has merit and aligns with our broader strategy. However, due to other priorities, we are unable to pursue it at this time. We’ll keep it on our radar and revisit it when the timing is right or if we see increased interest from our customer community.
-
Add Labor Code API Endpoint
Add Labor Code API Endpoints. When Enterprise clients add a new user, they currently assign all the applicable Sites and applicable Labor Codes manually. This can be extremely time consuming for clients with 50+ Sites and multiple Labor Codes for each Site.
1 vote -
Enhance GET/WorkOrder API Endpoint: Add 4 keys: entityKey, assetKey, budgetKey, workTypeKey.
GET/WorkOrder API: Request to enhance. Add 4 keys: entityKey, assetKey, budgetKey, workTypeKey. Currently, makes it unstable. Not Enterprise level. Thank you for the consideration.
1 voteApproved for Product Roadmap ·
AdminRobbie.Brannen@eptura.com
(Senior Product Manager, Eptura)
responded
Great news - your idea has been approved for inclusion in our product roadmap! Please note that the final feature set may evolve as we incorporate additional customer feedback, conduct product and design research, and consider broader use cases beyond the original request. We appreciate your input and will keep you updated as development progresses.
-
Enable PATCH/PUT Methods for Assets API Endpoint
The ManagerPlus API v2 currently supports GET and POST for
/Assets, but returns HTTP 405 for PATCH/PUT methods. This prevents programmatic updates to existing asset records.Use Case:
We need to bulk-update asset fields (descriptions, statuses, etc.) for our 2,400+ asset inventory without manual UI edits.Requested Feature:
Enable PATCH or PUT on/api2/Assets/{assetKey}to allow updating existing assets via API.Expected Behavior:
PATCH /api2/Assets/{assetKey}
{
"Description": "Updated value",
"StatusId": "ACTIVE"
}Would enable automated data quality workflows and reduce manual administrative overhead for maintaining accurate asset records.
1 voteThank you for your suggestion—this idea has merit and aligns with our broader strategy. However, due to other priorities, we are unable to pursue it at this time. We’ll keep it on our radar and revisit it when the timing is right or if we see increased interest from our customer community.
-
API Access to Complete Asset Field Schema
We need the ability to make API calls that retrieve or set any and all fields associated with asset records, including standard fields, custom fields, budget fields, hierarchy fields, and any other asset properties. Currently, the API documentation doesn't clearly expose all available fields or provide comprehensive endpoints for accessing the full asset schema. This would enable:
-Bulk operations on all asset attributes programmatically
-Complete asset records in API responses (not truncated/limited)
-Field discovery without reverse-engineering existing assets
-Integration with external systems that need to read(at least)/write all asset data (including status/state)
1 voteThank you for your suggestion—this idea has merit and aligns with our broader strategy. However, due to other priorities, we are unable to pursue it at this time. We’ll keep it on our radar and revisit it when the timing is right or if we see increased interest from our customer community.
- Don't see your idea?