What are APIs and how do APIs work?

API mobile phone

What is an API?

What is an API? We hear about how valuable APIs are all the time; our founder, Ross Mason, often says that they will have a significant impact on business. However, what is the definition of an API?

API stands for Application Programming Interface. An API is a software intermediary that allows two applications to talk to each other.  In other words,

4 key guiding principles to building your application network

The Application Network

In a previous post, I explained the reasons why pure SOA, despite being a powerful architectural paradigm with many benefits, could fall short.  Building on that narrative, I will provide in this post guiding principles to help you create a modern integration strategy – one that enables digital transformation, supports the API economy and is suitable for the pace of change required to build an application network.

No wasted time at CONNECT!

Conferences are great – they offer a chance to take a close look at floral carpet, eat food out of chafing dishes, and add to your lanyard collection. But they’re not great if they don’t offer sessions that are relevant to the work you’re doing and the problems you’re facing.

We’ve worked hard to eliminate that at CONNECT this year. From May 21-25 in San Francisco, we have numerous sessions that are specifically meant for developers working with Anypoint Platform.

The Four Secrets of a Great API

types of apis

Not all APIs are created equal – some are better than others. In fact, says ProgrammableWeb’s Adam DuVander, the not not-so-secret truth about APIs is that “creating a great one is really, really hard.”

As we know, APIs are becoming increasingly important assets to the business in and of themselves. A successful API is more than piece of code. When you view your API as a product or a way to add additional value to other parties,

MuleSoft releases API Workbench

MuleSoft has launched a beta release of API Workbench. This is an integrated development environment (IDE) allows developers to build RESTful APIs based on a design-first approach. API Workbench supports both RAML 0.8 and the newly launched RAML 1.0. RAML (RESTful API Modeling Language) is one of several API description specifications than can be used to design and document APIs.

API Best Practices: Spec Driven Development (Part 2)

November 20 2014

0 comments

This is part two of the API design best practices series.

Define Your API in a Flexible, but Standard Spec

I cannot stress the importance of spec driven development enough.  One of the quickest ways to kill your API is to define the API in your code, instead of coding to its definition.

New Series: API Design Best Practices

November 6 2014

2 comments

By now, you’ve probably already seen the image of the iceberg cross section showing just how many APIs are available out in the world. With over 13,000 public APIs available for use across the web, and hundreds of thousands more being used privately and in-house, the possibilities are endless.

The demand for flexibility and extensibility has driven the development of APIs and tools alike,

Designing your RESTful API for Longevity

motif

One of the greatest challenges API developers face is creating an API that is flexible enough to pass the tests of time and technology. In other words, creating an API that is built to last. Here are some tips to help you ensure your API has a happy, and long life expectancy – saving you a lot of frustration, and your company a lot of money!

“Unfortunately,

API First Development with RAML and SoapUI [Webinar]

motif

Tackling API development with an API first approach allows companies to focus on designing APIs to deliver business, rather than focusing on the nuts and bolts of implementing those APIs. With API first design, businesses can create an application programming interface optimized for adoption and once finalized, use a platform to rapidly implement it by connecting it to backend services.