The HTTP OPTIONS method and potential for self-describing RESTful APIs. The OPTIONS method is a somewhat obscure part of the HTTP standard that could be used today with a strong impact on the interconnectedness of the interwebs while requiring minimal effort.
It's role is well defined in RFC2616, yet no web services that I can find are taking advantage of it. To quote the spec: This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval. Minimally, the response should be a 200 OK and have an Allow header with a list of HTTP methods that may be used on this resource. Client Side API Mashups With CORS - Practice Over Theory. At Heroku we have APIs for pretty much everything.
Need logs for an app? Is that database available? You just beat someone at ping pong? There’s an API for that.
API Management Services | API - Tech Topics. Tools of the CityGrid Los Angeles Hackathon. Factual. Sort - API/Etc. Protocols | Development/Etc. REST | Protocols. API/SDK/Etc | Development/Etc.