<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The 'new and standard' way of structuring API requests and output is here, that I/We am/are trying to adhere to is here:<div class=""><br class=""></div><div class=""><a href="http://jsonapi.org/" class="">http://jsonapi.org/</a></div><div class=""><br class=""></div><div class="">For errors especially:</div><div class=""><br class=""></div><div class=""><a href="http://jsonapi.org/format/#errors" class="">http://jsonapi.org/format/#errors</a></div><div class=""><br class=""></div><div class="">greetings,</div><div class="">Jasper</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 22 Feb 2016, at 12:03, Robert Kisteleki <<a href="mailto:robert@ripe.net" class="">robert@ripe.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On 2016-02-22 11:08, Stephane Bortzmeyer wrote:<br class=""><blockquote type="cite" class="">Hello,<br class=""><br class="">IETF approved the future RFC draft-ietf-appsawg-http-problem "Problem<br class="">Details for HTTP APIs" which standardize structured error reports (in<br class="">JSON) to add machine-readable information to HTTP error codes.<br class=""><br class="">Would it be a good idea to convert current Atlas reports<br class="">({"error":{"status":400,"code":104,"detail":"__all__: Your selected<br class="">prefix is not covered by our network.","title":"Bad Request"}}) to the<br class="">new and standard format?<br class=""></blockquote><br class="">Thanks for the heads up! We'll look at this, most likely when it actually<br class="">becomes an RFC :)<br class=""><br class="">Regards,<br class="">Robert<br class=""><br class=""><br class=""></div></blockquote></div><br class=""></div></body></html>