Monthly Archives: October 2011

The websites or web pages preferring to stay private and having a password (Basic access authentication), normally returns HTTP 401 status which ends up being marked as “down” by Uptime Robot.

Uptime Robot now has support for monitoring password-protected websites by optionally mentioning the username-password in the monitor’s settings.

The feature exists for both HTTP and Keyword monitors and can be found in the “optional settings” link of “Add New and Edit Monitor dialogs”.

P.S. The API requests, responses and documentation are updated accordingly.

Besides being the developers of Uptime Robot, as website owners, we know that getting notified of downtimes instantly is so important.

Uptime Robot already has a wide range of notification methods: e-mail, text message, Twitter DMs, RSS and API.

Today, we are introducing a new notification method: push notifications for ─░OS -iPhone, iPad And iPod- through the popular and free iOS notification application Boxcar.

Usage is pretty simple:

Also, Boxcar has a Mac Desktop application which can also display the same notifications in your computer.

Does this mean Uptime Robot won’t have an iOS app?

No, it doesn’t. An iOS app for Uptime Robot is planned however we are currently focused on several other “most requested” features like reporting, website widgets and response time analysis.

Once, such core features are ready, we would love to launch a full-featured iOS app. But thought getting push notifications right now would be awesome.

After many requests from the users who would like to integrate Uptime Robot with their apps or create other interfaces for it (like a desktop or mobile), the Uptime Robot API is launched today which makes such integrations possible and so easy.

This is the v1 of the API which covers most of the important stuff including:

  • getting the list of monitors, their details (uptime ratio, URL, friendly name, type, etc.)
  • getting the notification logs for each monitor
  • getting the alert contacts notified after each notification
  • adding new monitors
  • editing monitors
  • deleting monitors.

It is a REST API that can return:

  • XML
  • JSON
  • JSON-p

responses.

In order to use it, simply get your apiKey from the My Settings page and head to the API documentation.

What's next with the API?

In the next version, we'll be adding:

  • "monitor-specific apiKeys" so you can securely use the apiKey in a client's website without revealing your main apiKey
  • methods for managing alert contacts (adding/editing/deleting them)

Please share your thoughts about the API and/or any other methods that you think should exist in the next version.