For more info on XML API 40 and REST API 40, see the Cisco Webex Meetings API Updates Overview (API 40). For updates for XML API 11 SP9 and earlier, go to Cisco DevNet. XML API 39.11.0 Updates Click here to download the XML API 39.11 schema. Teams are groups of people with a set of rooms that are visible to all members of that team. This API is used to manage the teams themselves. Teams are created and deleted with this API. You can also update a team to change its name, for example. To manage people in a team see the Team Memberships API. To manage team rooms see the Rooms API.
Please see the README on Github at https://github.com/nshimaza/webex-teams-api#readme
[Skip to Readme]| Versions [faq] | 0.2.0.0, 0.2.0.1 |
|---|---|
| Change log | ChangeLog.md |
| Dependencies | aeson, attoparsec, base (>=4.7 && <5), bitset-word8, bytestring, conduit, data-default, http-conduit, network-uri, optparse-applicative, text, utf8-string, webex-teams-api [details] |
| License | MIT |
| Copyright | 2017-2020 Naoto Shimazaki |
| Author | Naoto Shimazaki |
| Maintainer | Naoto.Shimazaki@gmail.com |
| Category | Web |
| Home page | https://github.com/nshimaza/webex-teams-api#readme |
| Bug tracker | https://github.com/nshimaza/webex-teams-api/issues |
| Source repo | head: git clone https://github.com/nshimaza/webex-teams-api |
| Uploaded | by nshimaza at 2020-07-29T15:12:25Z |
| Distributions | LTSHaskell:0.2.0.1, NixOS:0.2.0.1, Stackage:0.2.0.1 |
| Executables | webex-teams-api-exe |
| Downloads | 865 total (2 in the last 30 days) |
| Rating | (no votes yet) [estimated by Bayesian average] |
| Your Rating |
|
| Status | Docs available [build log] Last success reported on 2020-07-29 [all 1 reports] |
Modules
[Index] [Quick Jump]
- Network
- Network.CiscoSpark
- Network.WebexTeams
Downloads
- webex-teams-api-0.2.0.1.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Readme for webex-teams-api-0.2.0.1
[back to package description]A few months back I had been working on network automation and APIs via DevNet for different technologies and getting certified. I was spending some time exploring Webex Teams, bots, and thinking of use cases for integration. There are some really cool items that can be done for integrations and I began working on some of my custom home monitoring tools, like my garage opener. A Great benefit of using Webex Teams for this was that I didn’t need a separate app on my phone for this.
Then the pandemic happened and life changed – constant news reinforcing our primal fear instincts; groceries in scant supply; schooling issues for our children. I wanted to do something for our team to help keep spirits high.
Using the Webex teams SDK
I realized it would be really easy to create a very simple bot that had a very simple purpose, one positive message for people, every day. It was to be a Webex Teams space without a lot of discussion, just a positive message every day. Using the Webex Teams SDK and a handy Raspberry Pi, this was very easy to get going.
I quickly set up a Webex Teams bot on that Raspberry Pi, created a space, and told a few people about it. A few people invited some other people. Pretty soon we had 50 people and it was officially a “thing”. So I had to take my minimum viable project and improve some of the quotes in the list, which had been scraped from a repository on Github, and was… a good start. It had some cleanup to be done.
This portion of theDailyPositive bot was beneficial to me. While it was a personal project that I did in off hours, picking out good, uplifiting quotes was really positive for keeping mental sanity during this time.
Webex Api Integration
Over the course of four months this slowly expanded, reaching about 180 employees as of August 2020. But I had begun to experience a few operational challenges in sustaining this on my Raspberry Pi, notably a few hangs (likely due to a few other things I had running on it), and during some network upgrades (to support my new office layouts with kids at home), the Raspberry Pi had a few days where it was down. So whether the Pi just got tired, or had lost connection, there were a few times that the daily positive just did not run. I wasn’t feeling so positive about that.
Time to migrate this to the cloud
As I was doing some side integration work with creating some cloud capabilities for Webex Teams use cases, I had already poked in AWS to get some Teams messaging working. I decided for this project to use Google cloud platform so that I could gain exposure to that platform, for which I had another use case (involving Webex Teams).
The 2 key GCP functions to bring this to fruition were the Cloud Scheduler (for Cron like scheduling), and cloud functions. Tying these two items together allowed the function to run on a scheduled basis, similar to how my existing setup worked.
While the migration was pretty straight forward, as with everything, there were some challenges. These were initially ported into a cloud function in GCP. Some of the initial work done on the raspberry Pi included using the requests library and the Webex teams SDK. These weren’t available in GCP (at the time of writing), so I had to use standard HTTP posts using http library. This was not difficult to do, but required some thought. In addition, the cloud scheduler needed some IAM privileges to access the function. After working through those two items, I had a development room where I validated functionality, and after a few days migrated it to production.
The updated repo for the daily positive is here, containing both the Raspberry Pi code, and the gcp software. https://github.com/will0129/thedailypositive
A nice aspect of this, is the function is extremely lightweight and, with it only running once a day, doesn’t even scratch the surface on pricing. So this makes this migration a very affordable way to ensure that the daily positive can bring a bit of good news … daily … regardless of the state of my Raspberry Pi.
Webex Teams Rest Api Interview