In recent years, API specification/description formats, most notably OpenAPI, have become more common and have helped standardize the once-murky definition of an API. This standardization allowed the creation of a broad ecosystem of tooling for auto-generated testing and documentation.
- Articles (10)
- APIs (2)
- Mashups (0)
- SDKs (1)
- Libraries (0)
- Sample Source Code (0)
- Followers (1)
- Developers (0)
API Description Languages Articles
The following is a list of ProgrammableWeb articles that matched your search term. On an nearly 24/7 basis, ProgrammableWeb publishes new articles ranging from news to opinion to tutorials for both developers and API providers. All of our articles are categorized in such a way that you can find your way to related articles, APIs, SDKs, Libraries, Frameworks, Tutorials and Sample Source Code. If you have an interest in contributing any of the aforementioned content to ProgrammableWeb, be sure to read our guidelines for such contributions.
SmartBear has released a tool that it says is helpful for the testing that API providers might do during the API lifecycle. For example, it can reverse engineer an API definition by inspecting existing API calls. However, the experience is marred by several references to the Swagger specification.
Developer and Falcross creator Arman Dezfuli-Arjomandi has launched RESTyped, a specification for end-to-end typing for REST APIs with TypeScript. RESTyped is based on TypeScript, and it was created to bridge the gap between an API server and clients. RESTyped requires TypeScript 2.4+.
The first few decisions around building an API strategy centered on the business components. With those in place, building the API is now possible. The API strategy moves to becoming more of a technical concern for several steps as you resolve API design, security, and API Ops.
The Open API Initiative has announced that the OpenAPI 3.0.0 Specification is now available. This latest release of the OpenAPI specification includes new capabilities that were not part of version 2.0 such as support for Cookie parameters, new callback object, and new links object.
The Open API Initiative has announced that the final release of the OpenAPI 3.0 Specification is tentatively scheduled for release the week of July 17. A two-week last chance period will begin on June 19 giving developers a final chance to try out OpenAPI 3.0 and propose changes to the spec.
RepreZen has joined the Open API Initiative to collaborate toward a standardized way of describing REST APIs. The Open API Initiative falls under the open governance of the Linux Foundation. The consortium looks to collaborate on a standardized way of describing REST APIs.
In the world of API specs, RAML is a leading way to model API specifications while OAS (formerly Swagger) is the most common format for describing APIs. MuleSoft has joined the Open API initiative, believing that working together will improve both specs and afford value to the entire ecosystem.
On April 20th in San Francisco at MuleSoft's Connect conference, ProgrammableWeb's David Berlind is hosting two separate sessions. One is a panel discussion talking about options to the REST API architectural style and when they're appropriate. The other session is on building developer community.
Restlet has announced the availability of a new API documentation creation and publishing tool. The new tool is available as part of Restlet Studio and can automatically create API documentation from OAS and RAML files. The tool also includes several API documentation security options.