TheITJedi Posted Friday at 08:29 PM Share Posted Friday at 08:29 PM It appears the V3 API is out now. I see in the permissions when creating a token 'Get Device Custom Fields' as a permission, but there is no endpoint listed in the documentation. Additionally, attempting to use the new /api/v3/devices endpoint fails, it will however take the /api/v3/systems endpoint. This appears to return same information as v2 API does. Error returned is as follows: '/api/v3/devices' MessageDetail: No type was found that matches the controller named 'v3' My questions are: 1. is the /devices endpoint a new endpoint that's not available yet? 2. what is the endpoint to get a device's custom field? 3. is there at time line for getting the documentation updated? Thanks Link to comment Share on other sites More sharing options...
Administrators StefanMcl_Pulseway Posted Monday at 02:40 PM Administrators Share Posted Monday at 02:40 PM Hi @TheITJedi Thanks for reaching out, the following link should take you to all the documentation you will need regarding API V3 Just uses this link: https://<yourserverURL>/api and be sure to input your URL If you need anything else please let me know! Thanks, Stefan Link to comment Share on other sites More sharing options...
TheITJedi Posted Monday at 04:12 PM Author Share Posted Monday at 04:12 PM @StefanMcl_Pulseway, I have reviewed that documentation, it does not list anything for getting custom field values. Its listed in the API Token permissions here: But there is nothing in the documentation about it. The documentation shows that the endpoint for devices should be /devices, Attempting to call that endpoint results in this error: However, if I call the /systems endpoint (like for the V2 API but on V3), I get the same content I see from V2 API. What I need is the endpoint to get the custom fields for devices. Thanks, Link to comment Share on other sites More sharing options...
Administrators StefanMcl_Pulseway Posted Tuesday at 10:26 AM Administrators Share Posted Tuesday at 10:26 AM Hi @TheITJedi So the new update release for the API Authentication talks about API Access based on the Token. You can find it in the release notes here Fetching value on the Custom field is not yet available, what shows on the api documentation page is what we have open and that been said as we progress we will start adding support for the additional value. I hope this helps and if you have any more question please let me know Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now