-
Notifications
You must be signed in to change notification settings - Fork 30
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
[CGCP] Create endpoint to access conversation history #74
Comments
Hi!
Without these details, the ticket cannot be listed on the C4GT Community Listing. Please update the ticket |
Hey @chinmoy12c can I work on this issue. |
Sure go ahead. You'll find the documentation of the implementation here: https://uci.sunbird.org/use/developer/api-documentation/history-apis. This implementation currently resides on the transaction layer |
I am on it. |
Hey, @chinmoy12c sorry for the late response. I understand that in the Inbound repo, we have XmsgHistoryController which handles HTTP request for history API. We need to move this logic in uci-api to create an endpoint for accessing history api. But I can't figure out a way to do it. Can you please suggest me some steps or correct me if I am wrong? |
Currently, web channel uses transaction layer API to fetch conversation history. This will not be possible once the external access to the transaction layer is blocked. This endpoint should be exposed from UCI API itself.
Part of: Remove exposure of 9080 port in inbound
Project
UCI
Organization Name:
Samagra
Domain
Communications
Tech Skills Needed:
Nest.js, Java, SpringBoot, React
Mentor(s)
@chinmoy12c
Complexity
Low
Category
Security
Sub Category
API, Backend, Technical Debt.
The text was updated successfully, but these errors were encountered: