Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
As previously promised (although admittedly, a little late) I'll be walking you through the new Server-Sent Events (SSE) feature we're introducing in Prime Infrastructure 3.5. Please see the previous blog for an overview of SSE and why we're bringin...
Hey folks! While we're wrapping up the development of Prime Infrastructure 3.5 and preparing it for release, I thought I'd update you with some of the changes that we're bringing to the Prime Infrastructure API in 3.5.
Removal of DevNet Integratio...
I'm happy to announce that we now have Prime Infrastructure 3.3 available as an always-on sandbox, right here on DevNet. The sandbox provides access to our API, specifically read-only resources (most GET resources, excluding sensitive/credential res...
Hello again! We'd like to continue our series of blog posts with another Prime Infrastructure 3.2 preview. Please leave any feedback or questions you have in the comment section below. Just like in our last post, since we're talking about a produc...
Hey folks. As we wind down the development of 3.2, we wanted to preview some of the new features and enhancements coming to the API. We're looking forward to your feedback on what you like, dislike, and what you'd change. Since we're talking about...
Unfortunately no. We investigated adding support for this, as we called it "user-defined projections". Ultimately, there were too many impacts and issues caused by trying to support this, and only a few cases where there were noticeable improvement...
When you send a request for more than 1000 records you'll receive an immediate 503 response (unless the server is incredibly busy or there's a network issue, it shouldn't timeout).This limit is configurable, as you already know. However, increasing ...
In this case, the filter parameter should be:
cdpNeighbor.neighborIpAddress="X.X.X.X"
The "cdpNeighbor" parameter itself is what we call a collection. By filtering directly on it with an IP address, the Prime Infrastructure API framework won't be ...
Jesse, yes, the access point ID is a query parameter. It's name is "apId", so for an access point with an ID of 12345, the URL would be /webacs/api/v4/op/apService/rxNeighbors?apId=12345
The ID number itself can be retrieved from the GET data/Acce...
No, I don't think we currently expose that. We do report the base radio MAC address for each radio under the GET data/Radios and GET data/RadioDetails resources, but not BSSIDs. We'll look into adding that as a future enhancement.
