{"section":"known-issues","requestedLocale":"en","requestedSlug":"catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings","locale":"en","slug":"catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings","path":"docs/en/known-issues/Catalog/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md","branch":"main","content":"## Summary\n\n\nWhen using the catalog API collection, if a string JSON field is sent ending with spaces (for instance productName: \"myProductName    \") the catalog APIs will respond with an improper 400 response and empty response body, leaving the user clueless about what was sent improperly.\n\nThe correct response should still be a 400 (bad request) but with an error handling informing which field is incorrect and why.\n\n\n#### Simulation\n\n\nFor any catalog API (https://developers.vtex.com/docs/api-reference/catalog-api) insert 1+ empty spaces at the end of a string field, such as exemplified above.\n\n\n#### Workaround\n\n\nn/a\n\nThis type of string should not be accepted, but the error handling must be adjusted."}