| This document provides information relating to HTTP status codes when using the Airship Wallet API |
This article will outline:
- Common status codes
- Short tips for troubleshooting
Common status codes and tips:
400 - Invalid Request Parameters
Invalid Request Parameters error codes can be caused by attempting to create a pass under an existing external ID. External IDs are designed to allow passes to be generated once, then updated with new data on an ongoing basis.
401 - Unauthorized
Airship requires a base64 encoded combination of the Project Key and Project Secret in order to use the Wallet API. For more information see our documentation.
500 - Internal Server Error
This indicates that there is an issue on the Airship side that is causing the request to fail. This can be due to a number of factors including production incidents. Check out status page prior to contacting support if you are experiencing 500 errors from Mobile Wallet API endpoints.
406 - Not Acceptable Request
Most often these will happen due to missing data with the send. Is it a POST type sent with no valid JSON?
POST type requests will almost always need corresponding data such as the below JSON section:
-d 'json={"fronds": {}, "publicURL": {"type": "multiple"}}'
404 - The resource is no longer at that location
These can happen when you pass a correct API key but incorrect pass ID, or when trying to send a change to a pass that has not been installed to any devices.
Double-check the pass ID (please note this is not the external ID)
{"code":404,"description":"The resource is no longer at that location.","details":"object not found :Pass not found! Please pass a valid external Id instead of 1234567891011"}%
Related Content: