Skip to content

Implement the test API  #3

Description

@malkam03

The test API must be an interface with at least the following methods implemented:

Method Resource Param Body Result
GET https://url/activities/ BranchID*, ChapterID* - All IEEE activities of the chapter(if none provided, all branch activities)(if no branchID provided, return all IEEE activities)
GET https://url/branches/ BranchID* - Branch info(if no id is provided, return all branches)
GET https://url/chapters/ BranchID, ChapterID* - Chapter info(if no ChapterID is provided, return all chapters of the branch)
GET https://url/contacts/ BranchID, ChapterID* - Contacts List(if no ChapterID is provided, return branch contacts)
GET https://url/users/ UserID* - User Info(if no UserID is provided, return all users info)
POST https://url/users/ - User Info status code
GET https://url/notifications/ BranchID, ChapterID*,UserID* - Return a list of chat ids to notify, if no chapter ID provided returns all from the branch and if userid(chatid) is provided return the same chat id of a empty list

* optional parameters.
The request to that endpoints will return test example data. Not real data, the methods will only do that so that the @TEComputerIEEE/development-telegram-bot can work with that while the @TEComputerIEEE/web-api team implement the real API.

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions