Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

API #4

Open
Apexal opened this issue May 10, 2021 · 1 comment
Open

API #4

Apexal opened this issue May 10, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Apexal
Copy link
Owner

Apexal commented May 10, 2021

There should be a REST API served by the application for other apps to communicate with.

Example use case:
The ITWS server uses this bot to verify members, and then a separate bot is used to automate channel creation and such. It depends upon knowing the associations between Discord account and RCS ID, which in the latest version of this bot is not available unless directly connecting to the same database. If this bot served an API on a per-server-basis, an approved application could query for those associations.

@Apexal Apexal added the enhancement New feature or request label May 10, 2021
@Apexal Apexal self-assigned this May 10, 2021
@Apexal
Copy link
Owner Author

Apexal commented May 15, 2021

For extra security, an API request should only return the associations for users who are on the server of the api_key owner. API keys should be moved to clients instead of users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant