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

Update and Correct API References in ReportStream Responses #16660

Open
3 tasks
MikaelahD13 opened this issue Nov 25, 2024 · 0 comments
Open
3 tasks

Update and Correct API References in ReportStream Responses #16660

MikaelahD13 opened this issue Nov 25, 2024 · 0 comments
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team needs-refinement Tickets that need refinement from the team

Comments

@MikaelahD13
Copy link
Collaborator

MikaelahD13 commented Nov 25, 2024

Problem statement

[ NIH flagged that the API referenced in responses from ReportStream to retrieve a report’s history is incorrect. We’re updating the link to point to the correct API and adding an additional API that can be used to retrieve submissions for a sender in ReportStream.

What you need to know

Referring to this page on ReportStream website: https://reportstream.cdc.gov/developer-resources/api/documentation/responses-from-reportstream
Updated Content doc

Acceptance criteria

  • Publish the updated API documentation on the ReportStream website.

To do

  • Flag for Refinement:
    - Notify relevant stakeholders (engineering team) to review and refine the ticket.

  • Verify Ticket Placement:
    - Ensure the ticket is visible in the Next items column on the Zenhub board.

@MikaelahD13 MikaelahD13 added experience Team label to flag issues owned by the Experience Team needs-refinement Tickets that need refinement from the team engineering Work to be completed by an engineer labels Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team needs-refinement Tickets that need refinement from the team
Projects
None yet
Development

No branches or pull requests

1 participant