![]() Result.TrackingId is available in the Webex Teams API Client. ![]() The trackingId may be used on technical support of Cisco Webex Teams API side. Item.HasErrors and Item.GetPartialErrors() are available in the Webex Teams API Client. There are cases when Cisco Webex Teams API returns partial errors. and () are available in the Webex Teams API Client. There are cases when Cisco Webex Teams API returns error with error code and description. Result.HttpStatusCode is available in the Webex Teams API Client. Result.HasRetryAfter and result.RetryAfter are available in the Webex Teams API Client.Īlso, TeamsRetryHandler and TeamsRetryOnErrorHandler are available. Result.HasNext and result.ListNextAsync() are available in the Webex Teams API Client.Īlso, TeamsListResultEnumerator is available. PaginationĬisco Webex Teams API pagination is described on here. ProtectedString provides token encryption/decryption. Attach file from local stream is also available Membership is called 'SpaceMembership' in this API Client.Īvailable in v1.2.2. Room is called 'Space' in this API Client.Īvailable in v1.2.2. Get Me is also availableĪvailable in v1.2.2. Simple Webhook Listener/Server(.NET Standard 2.0+.Webhook secret validator, Webhook notification manager, Webhook event handler.AdaptiveCards attachment(Create Cards and Get AttachmentActions).Encrypt/Decrypt Webex Teams token in storage.Webex Teams Admin APIs(List/Get Event, License, etc.).Basic Webex Teams APIs(List/Get/Create Message, Space, etc.).Samples for Webex Teams API Client is available on here. NOTE: If you use Simple Webhook Listener/Server feature, CreateMessageAsync( space, "Hello, Webex Teams!! ") Title = "Demo space for Webex Teams API Client(Thrzn41.WebexTeams) ")Īwait teams. Say "Hello" to the specific named space. Iterates until getting all the spaces. Gets Enumerator to list all the Group spaces. It is an example that facilitates Guest Issuer of Webex Teams. Webhook listner, event handler in this APIClient has capablities to get these actions. You can use teams.GetAttachmentActionAsync() to get action from users. Success! We can now display all the specific about the ticket, but everything looks well formatted and easy to read for the end users.Ĭheck out Getting Started with Buttons & Cards to learn more about formatting and sending these UI snippets in Webex Teams.// Create From Json String. Let's improve our support ticket bot by using an adaptive card in the tech support room: An Adaptive Card in Webex Teams The Adaptive Cards framework allows us to insert small UI snippets - called cards - into the Webex Teams interface. Our users want more! What if they could see all the information included on a support ticket, without ever leaving Webex Teams?īuttons & Cards were introduced for Webex Teams in August 2019, and they are based on the Adaptive Cards framework from Microsoft. Using markdown allowed us to provide more data in a more readable fashion - which is a major improvement. This helps quite a bit! We can use rich text formatting to differentiate between the data in this message. Here's an example of a markdown formatted message: A 'markdown' formatted message in Webex Teams The Webex API basics guide provides some details on the specific options that are supported. Webex Teams does not support the full set of markdown formatting options, but the limited set it does support will allow us to improve the bot's message formatting. Markdown is a common formatting syntax on the web, touted as being easy to read and write. The support ticketing bot was a huge success! And now our users want more information details provided in Webex Teams so they can decide how important a ticket is directly from the tech support team chat. ![]() Our user can login to the support ticketing application and gather more information. We could include more, but that might look like a wall of text to the user. The message is straightforward, but doesn't include too much information. Our bot can let us know a new ticket has been received with a few pertinent details like the ticket number and company name. Let's consider a support ticketing application when a ticket is received, a bot could message the tech support room with a heads up: A 'plain text' message in Webex Teams As a user I send many plain text messages every day, and they achieve my goal! Using the API, bots can exchange plan text messages with users. Plain text probably the most common message format you'll find. One of these additions is support for 'in chat' buttons & cards.īuttons & cards add a new way to format messages in Webex Teams - before diving in, let's take a look at the previous message formatting options: Over the past year we've seen exciting new additions to the Webex Teams API that introduce some exciting new options for bots and integrations to interact with end users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |