Archive for the ‘Toolkits/API’ Category

h1

Introducing Myxer Services

August 9, 2007

Welcome to MyxerDev, the blog dedicated to the Myxer developer community. While we have yet to officially bless the official 1.0 release of our APIs and other services, we’ve already seen the launch of a lot of really cool website integrations and mashups of one sort or another that integrate Myxer’s mobile content platform. It’s a really exciting time for us, because we’ve been building the guts of this platform for a long time, and we’re finally at the point where sites other than MyxerTones.com are taking advantage of it.

Early adopters of Myxer Services have included:

  • bandVillage. Our new friend Peter integrated his PHP-based music portal with Myxer using the MyxerAPIs, allowing all of his bands to offer ringtones and wallpapers for sale right from his website.
  • Ringtones08.com. Jo and crew put together this politically-themed website that allows users to submit their own ringtones related to the ‘08 elections. What’s notable is that the site integrates seamlessly with Myxer despite being implemented entirely in client-side technologies (HTML and a touch of JavaScript). It takes advantage of MyxerFeeds to make this possible.

Our goal for Myxer Services is simple. Through our publicly-available interface, we will establish the already battle-hardened Myxer mobile content platform as the de facto standard for the creation, management, and provisioning of mobile content. From ringtones to videos to text messaging campaigns, we are committed to providing the absolute best way to mobilize your stuff.

We’ve spent the past two years insuring the system is powerful and scalable — it’s currently delivering more than two ringtones, wallpapers, songs, and videos every second of every day. And now, we’re focused on putting that power in the hands of every web developer on the planet, so that anyone can add mobile functionality to their own website, or build entirely new mobile products/services, that previously could only done through painstaking business arrangements with carriers, aggregators, and other shady and nefarious types.

So while today we’re still officially in “pre-release” mode, you’ll find the MyxerAPIs are already fairly well documented and fully-functional right now. Enhanced documentation, more examples, and a whole slew of new functionality is just around the corner, so keep your eye on this space!

Myk

h1

New profile method parameters

August 9, 2007

myxer.profile.create and myxer.profile.update optionally support the parameters biography, url (undergoes validation, prefixing http:// if it isn’t already there), file (profile image), and hometown so that partner sites don’t create such barren artist profiles.

Existing parameters have become more strict, too. For example, profile names can not contain profanity nor can they be empty.

h1

API Method Renaming

August 9, 2007

The following API methods have been renamed and the changes will be in production at the time of the next build:

myxer.profile.image => myxer.profile.setImage
myxer.ringtone.image => myxer.ringtone.setImage
myxer.video.image => myxer.video.setImage
myxer.song.image => myxer.song.setImage

h1

nav options removed from ui.ringtone.edit

July 7, 2007

If you are using the ui.ringtone.edit UI helper, you will be happy to see that we corrected the page template so that it no longer contains the main MyxerTones navigation options across the top. When you send users to this page, they will be returned to your sites ReturnUrl when they click either Cancel or Submit, and shouldn’t get distracted by the extra options.

h1

api.ringtone.add bugfix (now enforcing required params)

July 1, 2007

We updated the api.ringtone.add method yesterday which changes its behavior slightly. Whilethe name parameter has always been documented as required, we had previously allowed it to be omitted from requests. As of yesterday’s change, requests that omit the name parameter will fail with the appropriate error message. This is not likely to affect many people.
Throughout the Myxer APIs, every parameter not specifically marked as ‘optional’ is required, and requests that omit it will fail (bugs like this one notwithstanding!). We hope that by strictly enforcing these requirements we’ll contribute to the predictabililty of working with Myxer.