Here at MuleSoft, we talk a lot about how API-led connectivity can speed up your development cycles, and I’m here to guide you through how to do it. The API-led approach is a natural evolution from developing libraries, writing digestible markdown files, and sharing them on GitHub.
The world’s largest vendor-neutral API conference and expo, API World, is kicking off this week. And we are excited to announce that we will be on the ground from September 26-27 to talk about API program strategies, demo a solution using GraphQL APIs, show a fun demo that involves Twitter and a Commodore 64, and more!
Drop by booth 210 (left of the main entrance, near the lounge area),
Buffalo Wild Wings (BWW) – one of the top 10 fastest-growing restaurants in the U.S. – had one goal: to create a compelling restaurant experience for their customers. But in the modern retail world, this goal proved difficult as today’s customers expect a personalized experience.
In my role at MuleSoft, I advise federal agencies and commercial businesses in connecting their applications, data, and devices. Those conversations center around building modern Application Programming Interfaces (APIs) to create new capabilities. A modern API is one that enables systems to exchange information securely using broadly adopted standards like REST and JSON.
These days there are APIs for nearly everything, like an API for your thermostat. I can change the temperature in my house from my phone or my smartwatch using an application that interacts with my thermostat’s API.
An API fragment is a portion of an API specification, which is why understanding it starts at the API specification level. An API spec consists of a plan of how your API should look structurally – like a blueprint of a house.
The API spec documents what an API does and the expected call and response you can expect from it. It’s a key part of API development because it can help you isolate design flaws or problems before you write a line of code.
The size of the API economy is at an all-time high, with ProgrammableWeb reporting that there are over 17,000 APIs available on the web. The increasing demand for APIs has created a need to apply key API best practices.
But before you jump into creating APIs, in order to follow API best practices you need to ask yourself some questions. Why are you building an API? How should you mock your API?
I am excited to announce a new version of our open source API console. The 4.0 release comes with a completely new and responsive UI, improved capabilities for trying out your API, and additional tools to integrate automated builds into your CI/CD pipeline.
The API console can be run as a standalone web application or easily integrated into your own website, making it easy to incorporate into an existing developer portal with a fully branded layout.
Is it possible to have your cake and eat it too? In the world of API specs, we believe the answer is yes. We have been strong supporters of RAML, the RESTful API Modeling Language, since its inception, and we are if anything even more excited and committed about the value it brings to the API ecosystem.
Last week, we also joined the Open API Initiative of the Linux Foundation,
This webinar is now available to watch on-demand.
Last week, Gartner published its 2016 Magic Quadrant for Full Lifecycle API Management, which covers “the planning, design, implementation, publication, operation, consumption, maintenance and retirement of APIs.” Proudly, MuleSoft is in the Leaders quadrant for the second year in a row. In the report, Gartner lists the following as one of MuleSoft’s strengths:
- MuleSoft provides open-core enterprise service bus (ESB),
This is part 3 of my API security blog series. I will be showing an example scenario of how Anypoint platform can be a vital component of a secure API-led architecture and the capabilities to securing the API.
If you missed part 1 and part 2 here they are:
- API security: Ways to authenticate and authorize
- API security: Keeping data private but accessible