http://localhost/ticket/377 <p> When the API returns any response it should always retunr JSON. For example a 404 response should return something like </p> <pre class="wiki">{'status': 404, 'message': 'package somename not found'} </pre><p> When errors are encountered when creating a package: </p> <pre class="wiki">{'status': nnn, 'message': 'Validation Errors', 'errors':['description':'name cannot be blank', 'description':'license code must be an integer']} </pre><p> Not authorised: </p> <pre class="wiki">{'status': 503, 'message': 'You are not authorised to create this package.'} </pre><p> The reason being that screeds of html coming back in the response just makes it harder to debug and understand. Having the proper error codes/messages means that you can see why your package was not created. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/377 Trac 0.12.3 johnbywater Wed, 28 Jul 2010 13:21:49 GMT http://localhost/ticket/377#comment:1 http://localhost/ticket/377#comment:1 <p> Thanks a lot! I totally agree and have already started working on this. For example, try pointing your browser to <a class="ext-link" href="http://ckan.net/api/search/revision"><span class="icon">​</span>http://ckan.net/api/search/revision</a> (ie without any arguments). Also, there is probably a lot less HTML than there was, since the errors are not handled as if it was an error within the "Web" user interface. At any rate, perhaps we could work through the error cases, filling in the tests as we go? I think it's just unworked ground, rather than anything deliberate. :-) </p> Ticket thejimmyg Fri, 07 Jan 2011 14:28:18 GMT http://localhost/ticket/377#comment:2 http://localhost/ticket/377#comment:2 <ul> <li><strong>owner</strong> set to <em>thejimmyg</em> </li> </ul> Ticket ross Mon, 28 May 2012 11:58:50 GMT http://localhost/ticket/377#comment:3 http://localhost/ticket/377#comment:3 <ul> <li><strong>owner</strong> <em>thejimmyg</em> deleted </li> <li><strong>repo</strong> set to <em>ckan</em> </li> <li><strong>theme</strong> set to <em>none</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>assigned</em> </li> </ul> <p> We have another ticket for fixing the API </p> Ticket ross Mon, 28 May 2012 11:59:09 GMT http://localhost/ticket/377#comment:4 http://localhost/ticket/377#comment:4 <ul> <li><strong>status</strong> changed from <em>assigned</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>wontfix</em> </li> <li><strong>milestone</strong> set to <em>ckan-future</em> </li> </ul> Ticket