https://github.com/hugorodgerbrown/HipChat.net

C# wrapper for HipChat API (maintainers required!)
https://github.com/hugorodgerbrown/HipChat.net

Last synced: 14 days ago
JSON representation

C# wrapper for HipChat API (maintainers required!)

• Host: GitHub
• URL: https://github.com/hugorodgerbrown/HipChat.net
• Owner: hugorodgerbrown
• Created: 2011-02-17T14:53:01.000Z (over 13 years ago)
• Default Branch: master
• Last Pushed: 2021-10-02T11:26:43.000Z (about 3 years ago)
• Last Synced: 2024-10-02T00:38:59.963Z (about 1 month ago)
• Language: C#
• Homepage: http://nuget.org/List/Packages/HipChat.Net
• Size: 1.41 MB
• Stars: 45
• Watchers: 8
• Forks: 45
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

README

        
#HipChat.Net Client library

**UPDATE**

I no longer use .NET, and do not have a working, stable .NET development environment set up, which makes maintaining this project a PITA. If anyone would like to take it over (specifically the packaging for Nuget, which is the hard part to do without a dev environment), please get in touch.

---

This is a C# library used to wrap the [HipChat API](https://www.hipchat.com/docs/api)

The API is very clear and concise, so there's not much to add to this - this library just makes the formatting of the URL a bit simpler. The API returns either XML or JSON, and the client library contains native POCO representations for those who like those sorts of things. 

NB This is NOT for mission critical, transactional, guaranteed delivery!

The API supports four methods:

1. Fetching a list of available chat rooms

2. Sending a message to a room

3. Fetching the chat history from a room

4. Showing the room details (who's in it etc.)

Access to the API is managed by the inclusion of an `auth_token` with each request. The auth_tokens are managed from the HipChat admin panel, by the account holder.

The core use case for this library is to allow developers to include 'bots' in chat rooms. The sub-cases included to support this are therefore:

1. Administer the 'bot' - which would involve selecting a room from a list of rooms, and entering the auth_token, and possibly a fixed "sender" id.

2. Sending the messages.

I have not, therefore, coded up the chat history or room details API methods.

```c#

Usage:

// to set up a local instance of the client

var client = new HipChatClient(auth_token, room_id, name_of_sender);

// send a message

client.SendMessage("Hello World!");

// for one-off use, there is a static method - NB this creates an instance internally, so 

// only use when making one-off calls.

HipChatClient.SendMessage(auth_token, room_id, name_of_sender, "Hello World!");

// optional the hipchat server can be set to a hipchat enterprise server

client.ServerName = name_of_server;

```

##TODO

1. Proper validation of message XHTML to ensure it won't be rejected by the API

2. Add in history/show methods

##LICENSE

(The MIT License)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.