From API designer, save resuable API fragments, such as security schemes or data types, into Exchange with one click. Anyone within your organization can then reuse the API fragments to build APIs faster, in a consistent manner. Once the API is built, save it into Exchange for consumption within flow designer or Anypoint Studio.
RAML and OAS
RESTful API Modeling Language (RAML) and OpenAPI Specification (OAS) are machine readable design specifications that can be easily understood by non-technical audiences. Without writing a single line of code, designers can perfect their API through active collaboration on API requirements with customers, partners, and internal engineers.
Interactive API Console
The real-time console provides a visual representation of how each API resource and method will function as it is created. The console doubles for interactive documentation, meaning designers and future users can see how the API will function and preview the API’s documentation before writing a single line of code.
As designers create the API specification, the context-aware shelf within API designer auto-populates with methods, resources, parameters and security components that are the most appropriate for the current API being designed, allowing you to follow best practices in a consistent manner.
With the mocking service, designers can share a real-time mock of the API design with other teams or engineers, allowing teams develop applications in parallel to API development, speeding delivery and ensuring APIs meet business requirements.
“As more and more APIs are defined by RAML, API design improves and becomes more consistent. Good API design helps developers maximize productivity and flexibility, eliminating the need to waste countless hours struggling to consume RESTful APIs.”