SPSCommerce sps-api-standards Discussions
Discussions
-
You must be logged in to vote -
You must be logged in to vote PATCH requests on list with mutable and immutable properties
clarificationClarity on API Standards was needed (no changes). -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote Pagination Options & Support
minor-changeSmall non-breaking modification to existing API Standard details. proposalNew idea for discussion within the API Standards. -
You must be logged in to vote All path resources should be followed by a unique identifier for that path resource
clarificationClarity on API Standards was needed (no changes). minor-changeSmall non-breaking modification to existing API Standard details. proposalNew idea for discussion within the API Standards. -
You must be logged in to vote Prefixing Internally Generated IDs with "sps" (i.e. spsOrgId)
proposalNew idea for discussion within the API Standards. -
You must be logged in to vote Misusing instance field in the problem description of the error response
clarificationClarity on API Standards was needed (no changes). -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote 404 vs 403 for unauthorized requests to prevent data leaks
minor-changeSmall non-breaking modification to existing API Standard details. proposalNew idea for discussion within the API Standards. -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote 5xx Series Status Code Usage (i.e. 500 vs 504)
minor-changeSmall non-breaking modification to existing API Standard details. proposalNew idea for discussion within the API Standards. -
You must be logged in to vote Handling complex object payloads in API Responses
minor-changeSmall non-breaking modification to existing API Standard details. -
You must be logged in to vote -
You must be logged in to vote Authorization Header Support for Case Insensitive Token Type ("Bearer" vs "bearer")
minor-changeSmall non-breaking modification to existing API Standard details. proposalNew idea for discussion within the API Standards. -
You must be logged in to vote Proper JSON Serialization of Long/BigInt/Int64
clarificationClarity on API Standards was needed (no changes). minor-changeSmall non-breaking modification to existing API Standard details. -
You must be logged in to vote Variability between property name prefixing
major-changeContract breaking modification to existing API Standard details. -
You must be logged in to vote Inclusion of Null data values in serialized API output
major-changeContract breaking modification to existing API Standard details. -
You must be logged in to vote ETags and a Persisted Version Reference for An Object
clarificationClarity on API Standards was needed (no changes). -
You must be logged in to vote X-Request-ID Header Replacement / Conflict
clarificationClarity on API Standards was needed (no changes).
