(If this post belongs elsewhere, please let *me* know). My plan is to describe in words what I want (e.g. oauth 1.0 *and* oauth 2.0 authentication options, and all the details of my: account creation, data submission, and report generation options, plus also my async/oob event callbacks).
Your job is to write best-practice implementation with full stub/placeholder doc/comments/options/etc. I will then take over and finish the API specs, then code APIs to honor them. Payment will be via PayPal to suit your rates and comfort. I will * Use OAuth 2.0 for authentication principally (but I desire to support 1.0 *as well*, for my friends without ability to support SSL) * be RESTful, default to JSON, but support xml, text, etc as well (using dots to serve back non-json (.xml)) * use camelCase verbs in plural * have only 2 base URLs per resource (one for collections, other for items) * put variations after the "?" * put lots of useful stuff into errors (include codes, clear english-readable explanations, and moreInfo links) * use ?limit=10&offset=0 for pagination * support partial responses * and make it possible for crippled clients to still work (allow "?method=put" for stuff that cannot HTTP PUT, and ?suppress_response_codes for stuff that chokes on HTTP "non-200" replies). *alternatively*: if you have seen an absolutely outstanding example of someone else already doing the "perfect" swagger API and want to nominate them, I'm happy to adapt their solution to my needs as well. Chris. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
