Skip to content

Update the existing Webex Teams API wrappers and data models #127

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
15 tasks done
cmlccie opened this issue Jul 10, 2020 · 2 comments · Fixed by #128
Closed
15 tasks done

Update the existing Webex Teams API wrappers and data models #127

cmlccie opened this issue Jul 10, 2020 · 2 comments · Fixed by #128
Assignees

Comments

@cmlccie
Copy link
Collaborator

cmlccie commented Jul 10, 2020

Review the existing Webex Teams API wrappers and data models and ensure they are up-to-date with all posted parameters, attributes, and sub-endpoints published on developer.webex.com.

  • Access Tokens API
  • Admin Audit Events API
  • Attachment Actions API
  • Events API
  • Guest Issuer API
  • Licenses API
  • Memberships API
  • Messages API
  • Organizations API
  • People API
  • Roles API
  • Rooms API
  • Teams API
  • Team Memberships API
  • Webhooks API
@cmlccie cmlccie added this to the v1.x milestone Jul 10, 2020
@cmlccie cmlccie self-assigned this Jul 10, 2020
@cmlccie
Copy link
Collaborator Author

cmlccie commented Jul 10, 2020

@sQu4rks, I have reviewed and updated all of the existing wrapped APIs except the Rooms API. I'll review this one after your PR with the meeting info API endpoint update.

@sQu4rks
Copy link
Contributor

sQu4rks commented Jul 11, 2020

@cmlccie The /rooms API matches the implementation in the sdk so I think we can, after merging PR #129, close this issue as all endpoints are up to date.

cmlccie added a commit that referenced this issue Jul 11, 2020
#127 Update the existing Webex Teams API wrappers and data models
@cmlccie cmlccie closed this as completed Jul 11, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants