SOAP & REST Attachments in Mule

motif

I was recently working on a project where we had to handle SOAP attachments. Working with SOAP attachments is the kind of thing that you work on every 3-5 years and then 10 seconds after you are done you forget all about them. All the information required is available in our docs but it can still be good to have a complete end to end example as a reference. Esteban Robles Luna’s (former MuleSoft colleague) blogpost,

Anypoint Platform for APIs – February 2015 release

February 24 2015

2 comments

I am extremely happy to announce a significant set of updates to Anypoint Platform for APIs that were introduced this month. These updates will make it easier for API owners and administrators to publish their APIs in a way that is sure to further their successful adoption. The sections below describe the core new capabilities introduced in this release.

Instant management through automatic deployment

The management of APIs with Anypoint Platform consists of the deployment of a proxy application to an API gateway runtime.

New RAML Tools for .NET Developers using Anypoint Platform

February 19 2015

0 comments

guest_postguest_post

This post is brought to you by Pablo Cibraro. Pablo is a Software Architect focused on MuleSoft’s solutions for Microsoft.

 

As part of our on-going effort to make Anypoint Platform even more accessible and intuitive for .NET developers, we are thrilled to introduce a RAML parser and Visual Studio extensions that make it easy to consume and implement APIs using RAML.

Developer Spotlight: Chocolabs

motif

To app your life, CHOCOLABS takes an API-first approach

CHOCOLABS is one of the largest app publishers in Taiwan with over 50 iOS/Android entertainment focused apps under their belt. We recently spoke with Jerry Weng, one of their co-founders, to talk about building a team, finding a niche, and driving business growth with the right development tools.
Q – Indy | A – Jerry

Q: Who is CHOCOLABS?

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.

Q&A: How to Build a Successful API Program

October 31 2014

0 comments
motif

Thanks to those of you who attended our webinar last week, “The API Love Triangle: Delivering Successful API Programs,” and we hope that you found the session valuable. Now you know that the API love triangle is composed of three key people and that the success of your API program depends on satisfying the needs of each:

  • The API Developer,

Join Us for a FREE, Virtual API Conference!

October 23 2014

0 comments
motif

MuleSoft has teamed up with DayCamp4Developers to put together one full day of API talks by today’s thought leaders. Best of all, this event takes place online. That means anyone with a browser can attend, and it’s FREE!

You’re not going to want to miss this exciting event where our speakers will be talking about the API landscape, building and designing your API, and ensuring that developers use it.

Latest Release – Anypoint Studio, Mule 3.6.0-M2 & 3.5.2

motif

Anypoint Studio October 2014, Mule 3.6.0-M2 and 3.5.2 released

Today we’re releasing Anypoint Studio October 2014, Mule 3.6.0 – Milestone 2 (M2), and Mule 3.5.2. This release includes new HTTP capabilities which make it easy to connect to RESTful APIs with RAML, and productivity enhancements inside Anypoint Studio – such as DataSense for APIkit and a new Studio launcher.

How RAML Saved My Email

motif

In today’s post, I’d like to tell you a short story about a bizarre love triangle between a server-side application (Gmail), a client (Mailbox), and the “hero of the day” (API Notebook).

Before starting, let me mention that API Notebook is a web-based, persistent, JavaScript scripting workspace that enables live testing and exploring of APIs. It’s an example of literate programming.

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,