[PDB-tech] Additional API End Points

[Anna Claiborne]

And I thought of a few more:

Not sure what you would want to call this - something to pull the latest peers at an exchange with a date as a and public/private as parameters.  For example, you could pull the latest peers at an exchange, or group of exchanges in the last two weeks (or day, or month, or whatever) OR pull only the new private peers at an exchange added in the last week.

Probably have some other ideas that I’ll just keep adding.

-Anna


> On Jul 23, 2015, at 9:14 PM, Andy Linton <asjl at nsrc.org> wrote:
> 
> Yes please!
> 
> 
> 
> On Wed, Jul 22, 2015 at 10:25 AM, Anna Claiborne <anna.claiborne at gmail.com <mailto:anna.claiborne at gmail.com>> wrote:
> Hello
> 
> The new API, while nicely put together, is missing some easy to use end points for common tasks.  When the mysqldump file is finally deprecated, collecting this information would require getting all the data through multiple API calls and sorting/counting programmatically, rather than just a simple mysql query.  For ease of adoption, I’d like to suggest adding the following end points:
> 
> countPeers - The count of peers at an exchange
> exchangePeers - All peers at a particular exchange.  A flag to include all their IP information would be great.
> peerExchanges - All exchanges a peer participates in.  Again, flag to include IP info.
> 
> I’m sure there are more, but these are easy ones.
> 
> -Anna
> _______________________________________________
> Pdb-tech mailing list
> Pdb-tech at lists.peeringdb.com <mailto:Pdb-tech at lists.peeringdb.com>
> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech <http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/pdb-tech/attachments/20150731/672b8ceb/attachment.html>