-
Notifications
You must be signed in to change notification settings - Fork 5
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
NIAD-3234: endpoint docs update #1024
Conversation
parameters: | ||
- name: request | ||
in: query | ||
required: true | ||
schema: | ||
$ref: '#/components/schemas/EhrStatusRequestQuery' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my understanding, is this saying you can pass the filtering parameters in via query parameters? Also it's a bit strange it's marked as required, given that I don't think I've ever used the /requests
endpoint in this way. 🤔
toAsid: "200000000359" | ||
fromOdsCode: "P883302" | ||
toOdsCode: "P113302" | ||
required: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I'm pretty sure I've also called this endpoint without specifying a request body and it's worked. 🤔
Any "in-progress" transfers are excluded from this list, but become available once they either succeed or fail. | ||
|
||
Requests can be made to the following endpoint, where each attribute within the JSON POST body is an optional filter criteria. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Related to my comments below about required
, this comment reaffirms my understanding which is that the filtering is optional.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I see, make sense, I will look into it and adjust it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think as object it is required but EhrStatusRequestQuery object has fields which are not mandatory and can be empty.
Looks good. No mutations were possible for these changes. |
Quality Gate passedIssues Measures |
What
Endpoints documentation update
Why
The documentation must remain synchronized with the code implementation to ensure accuracy, clarity, and ease of use. This alignment minimizes confusion, reduces the risk of errors during integration, and provides developers with reliable information to effectively utilize the API.
Type of change
Please delete options that are not relevant.
Checklist: