-
Notifications
You must be signed in to change notification settings - Fork 19
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 docs with return payload #469
Conversation
We have previously gone with the standard of leaving HTTP status codes to any network level issues/infra, and always returning 200 with an error message for any application level errors. To stay consistent, I'd recommend we do that here as well to match other platform APIs |
Sure thing -- I'll remove references but I am curious about the reasoning here. In general I think that there is value in distinguishing between client caused failures and internal errors |
Why this should be merged
Returns error status codes and adds response documentation to the signature aggregator API
How this works
How this was tested
How is this documented