Inconsistent HTTP Status Codes for Request Validation

Hello Snipcart Support,

I’m currently integrating the Snipcart API into my project and I’ve encountered an inconsistency with the HTTP status codes returned by the request validation endpoint ({snipcart_request_token}).

According to the HTTP specification, a status code of 200 OK should indicate that a request has been processed successfully. However, when I validate a request token using a GET request to the aforementioned endpoint, a status code of 405 Method Not Allowed is returned even when the token is valid.

This is causing confusion and complications in handling responses from your API, as a 405 status code typically indicates that the HTTP method used (in this case GET) is not supported for the requested resource.

Here’s an example of a curl command I used and the response:

curl -IH "Accept: application/json" \ \
  -u S_my-key:
HTTP/2 405 
content-type: application/json; charset=utf-8
date: Sun, 07 May 2023 07:03:44 GMT
access-control-expose-headers: Request-Context
allow: GET
cache-control: no-cache
expires: -1
pragma: no-cache
content-length: 137
request-context: appId=cid-v1:48f65c7b-986c-4ec3-89de-eb0160f55639

Yet, the body appears to reference my token, resource and such correctly.


Could you please look into this issue and clarify why a 405 status code is returned for successful request validations instead of a 200 status code?

Thank you for your time and assistance.

Best regards,