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.
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
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.
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
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.