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.
- Articles (32)
- APIs (0)
- Mashups (0)
- SDKs (0)
- Libraries (0)
- Sample Source Code (0)
- Followers (1)
- Developers (0)
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.
During MuleSoft's annual conference in San Francisco, the company announced the June 2017 "Crowd" release of its Anypoint Platform. The new version is designed to help organizations capitalize on the re-usability of developer assets like APIs by making them easier to promote, discover, and consume.
Looking to bring its suite of API tools into one UI that makes it possible for users to more easily transition between tasks like API consumption and deployment, Restlet has announced a new version of its namesake Studio offering. On the design front, Studio also supports data structure nesting.
Postman is the Chrome app and Cloud collaboration tool that integrates into your existing workflow to simplify the process of prototyping and testing APIs. In this tutorial, Kumar Gaurav explains a simple process for getting Postman to detect and import all RAML API definitions from inside a folder.
RAML makes it easy to manage the entire API lifecycle, from designing to documenting to sharing. This article discusses several patterns for auto-generating C# code for provisioning APIs by establishing a shared RAML that reduces friction between frontend and backend developers.
This tutorial on Appnovation shows followers how to access a SOAP API backend from a RAML API frontend by reverse engineering a MuleSoft Web Services Consumer example. The author provides step-by-step notes and the source code is available in the APIKit Console hosted on CloudHub.
MuleSoft has released API Workbench, a free integrated development environment (IDE) for building RESTful APIs based on a standard, design-first approach. API Workbench supports RAML 1.0, an API description specification that developers can use for designing and documenting APIs.
The RAML 1.0 specification has been published and features new data-typing system, enhanced examples support, libraries, overlays and extensions, annotations, and more.
MuleSoft has announced that the MuleSoft Enterprise Anypoint Platform now features automatic SDK generation via integration with APIMATIC. The integration makes it possible for Anypoint users to quickly generate SDKs for an API that can be offered for download in the API portal.
RAML 1.0 Final Candidate is coming soon and will include significant improvements to data types, examples, annotations, overlays, libraries, and more. RAML stands for RESTful API Modeling Language and is based on YAML, and allow developers to document APIs in a human-readable form.