zulip/api
Keegan McAllister bd7b7adb6b Rename api.common to humbug
Fixes #482.

(imported from commit 1bd6a7fd993d8d5e225e0311c288dbce0c369a40)
2012-12-03 15:54:54 -05:00
..
bots Rename api.common to humbug 2012-12-03 15:54:54 -05:00
examples Rename api.common to humbug 2012-12-03 15:54:54 -05:00
README api: Extend documentation a bit. 2012-11-27 12:09:56 -05:00
__init__.py Update post-receive hook to send messages via the API. 2012-10-03 14:32:05 -04:00
humbug.py Rename api.common to humbug 2012-12-03 15:54:54 -05:00

README

#### Dependencies

The Humbug API Python bindings require the following Python libraries:

* simplejson
* requests (version >= 0.12)

#### Using the API

For now, the only fully supported API operation is sending a message.
The other API queries work, but are under active development, so
please make sure we know you're using them so that we can notify you
as we make any changes to them.

The easiest way to use these API bindings is to base your tools off
of the example tools under api/examples in this distribution.

If you place your API key in ~/.humbug-api-key the Python API
bindings will automatically read it in.  You can obtain your Humbug
API key from the Humbug settings page.

A typical simple bot sending API messages will look as follows:

At the top of the file:

    # Make sure the Humbug API distribution's root directory is in sys.path, then:
    import api.common
    humbug_client = api.common.HumbugAPI(email="your_email@example.com")

When you want to send a message:

    message = {
      "type": "stream",
      "to": ["support"],
      "subject": "your subject",
      "content": "your content",
    }
    humbug_client.send_message(message)

Additional examples:

    client.send_message({'type': 'stream', 'content': 'Humbug rules!',
                         'subject': 'feedback', 'to': ['support']})
    client.send_message({'type': 'private', 'content': 'Humbug rules!',
                         'to': ['user1@example.com', 'user2@example.com']})

send_message() returns a dict guaranteed to contain the following
keys: msg, result.  For successful calls, result will be "success" and
msg will be the empty string.  On error, result will be "error" and
msg will describe what went wrong.