-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add GET/POST/DELETE /configuration/apiKeys #128
Comments
Here are my recommendations for RESTful design:
For POST /configuration/apiKeys, the assumption I've made from the API docs is that the For now, there is no GET /configuration/apiKeys/{apiKey}, but can be added as a future enhancement based on demand. |
* #123 - Add AWS XRay Support to Lambda functions * #124 - OCR Tessaract Support * #126 - add GET/PATCH /configs API endpoints * #125 - ChatGPT Tag "documentTagging" Support * #127 - Add "apiKey" access support * #126 add GET/PATCH /configuration API endpoints * #128 - Add GET/POST/DELETE /configuration/apiKeys * added contentLength to GET /documents/{documentId}/fulltext, POST /searchFulltext * #10 - Version delete corrupts all other versions of file, including current * moved awstests under integration src package
Allow the ability for the admin user to create API Keys to access the API.
The text was updated successfully, but these errors were encountered: