Archive for the ‘API’ Category

You may have noticed that when a user tries to subscribe with the signup panel and fails three times, it shows the following message:

Previously, a user would have to contact us with their phone number and we’d reset their panel so they could try again.

We’ve changed the panel so that it automatically resets after 15 minutes of being in the “Oops!” state. Now users will be able to try re-subscribing without our intervention.

I’ll be updating the panel copy shortly and also fixing that glaring typo! Can you find it?

A lot of you have been asking to send ad-free messages, so we made it easy! Choose a plan according to your outgoing SMS volume, make a small code change, and you’re set!

Check out the Ad-free Plans.

Ad-supported messages will remain free and will contain a short advertisement.

How does it work

Once you sign up, you’ll need to add ad_free=”true” to each message that you’d like to send without an ad.

Check out the updated docs for more info.

Questions?

For more information, check out the ad-free FAQ.

Happy developing!

We’ll be doing some maintenance work on our servers and will have to shut down message delivery for about three hours starting at 9PM on Sunday, November 20, 2008. During this update, we’ll be:

• Performing some back-end improvements
• Switching to new servers
• Implementing Ad Teaser delivery

The only difference once we’re back up again is that you might start seeing some Ad Teasers being placed in SMS messages sent by your apps.

Let us know if you have any questions or concerns.

We just posted a couple of PHP examples in our Google Group. Both examples were provided by Zeep Mobile developers, we haven’t verified that they’re working, but we hope some intrepid PHP slingers can pitch in.

First - Generating the authentication string with PHP
This one was provided by Sam Keen from http://Shizzow.com

Second - Generating an authenticated header with PHP
This was provided by Brian Hendrickson from http://openmicroblogger.com

Give these a try if you’re looking for help with PHP and let us know how it turns out.

PS - If I’ve mislabeled what these samples actually do, let me know ASAP (I push pixels around here, not 1s and 0s)

Just got word that our API now works with AT&T. The last major carrier we’re waiting on is T-Mobile, which should be ready to go within a week. There’s a complete list of supported carriers on the Beta Page.

Now you can send SMS texts from Python as well.

Grab the code from source at: http://code.google.com/p/zeep-messaging/

Or if you have setuptools installed run $ easy_install zeep.sms

We’ve whipped up a home for client libraries and the project is being hosted at google:

http://code.google.com/p/zeep-messaging/

So far, a Ruby client has been commited. Let us know what other languages would you like to see.

The rdoc for the Ruby client is available here.

Yup, we’re in Beta!

After tons of sweat, tears, ones, zeroes and some pixels, we’re finally releasing our Zeep Mobile SMS Messaging API into the wild. We’re setting it free…metaphorically AND literally. You see, it’s absolutely free for developers AND subscribers to use. Developers pay no delivery costs for their messages, and subscribers pay no additional charges to receive them. We’re still in beta so you’ll definitely notice some hiccups with our service and site, but we’re keen for developers to start experimenting and integrating the API.

So, what exactly does it do?

In a nutshell, our API allows any web application to send and receive mobile content to and from its users. We provide a handy mobile settings panel that can be embedded into any web application, through which users can subscribe to that application’s mobile content. Once users complete the subscription process, they’ll be able to receive any alerts and messages from that application on their mobile device. The examples are endless–weather alerts, sports score updates, stock tips… anything! Beyond sending messages, applications using Zeep Mobile can also receive mobile content from their users. There’s no easier way to get web application mobile than Zeep.

Currently the Zeep Mobile API only communicates with mobile devices in the United States, although we’re looking at expanding our reach in the futures. Developers without access to a US mobile device can use our Virtual Test Phones to test and develop their mobile features.

Why does it rock?

We looked far and wide to find a good mobile content solution for our own projects in the past, and simply couldn’t find one. We saw an opportunity to fulfill a need and jumped on it. Here’s why we think developers will love our API:

• It’s super easy to integrate with any web application
• We do the hard work of properly subscribing users via our embeddable mobile settings panel
• It’s absolutely free for developers AND subscribers (standard carrier charges apply for subscribers)
• There are no volume restrictions on messages

Getting started

Sounds pretty sweet so far, eh? If you’re itching to get started, we’ve created a handy guide to help you take your first steps towards integrating Zeep Mobile in your current or next project. Take a look…

Getting Started Guide

About the Beta

During the beta phase, we’re limiting outgoing messages to a small set of developer numbers (which each developer can add up to 10 numbers to). We want to take some time to gather feedback and refine our service before we start sending a lot of volume.

More about the beta

We want your feedback!

Since we’re in the Beta phase, we’re very keen to hear your feedback. Leave your comments, thoughts, ideas, or gripes in the comments below. We’ll be sure to keep a close eye on them. You can also contact us directly. Let us know what you think!