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

Issue Report: /en-us/data-provider/hashed-records #288

Open
smitbaranwal opened this issue Jun 24, 2024 · 1 comment
Open

Issue Report: /en-us/data-provider/hashed-records #288

smitbaranwal opened this issue Jun 24, 2024 · 1 comment
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@smitbaranwal
Copy link

Describe the bug
The documentation for the /dp/records/hashed API incorrectly describes the 413 error type. Currently, it indicates that a 413 error signifies an "unauthorized" error, which is incorrect. The 413 error should correspond to a "Request Entity Too Large" error, indicating that the request size exceeds the server's limit.

URL of the content
https://advertising.amazon.com/API/docs/en-us/data-provider/hashed-records#tag/Hashed-Records/operation/UploadHashedRecords:~:text=RESPONSE%20SCHEMA%3A%20application/vnd.dpuploadhashedrecordsresponse.v3%2Bjson

Description of what the documentation currently says
In the section describing the error codes for the /dp/records/hashed API, the documentation currently states that a 413 error signifies an "unauthorized" error.

Description of what the documentation should say
The documentation should correctly describe the 413 error type as "Request Entity Too Large." This error occurs when the size of the request exceeds the server's maximum allowable limit.

Screenshots
image

Additional context
This incorrect description can lead to confusion and misdiagnosis of issues when developers are troubleshooting problems related to request size. Ensuring that the documentation accurately reflects the nature of the 413 error will help developers understand and resolve issues more efficiently.

@smitbaranwal smitbaranwal added bug Something isn't working documentation Improvements or additions to documentation labels Jun 24, 2024
@glmcmull
Copy link
Contributor

Thanks for the report! I'll forward this bug to the appropriate team so that they can address the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants