Troubleshooting

Debugging Common Failures

If you encounter failed tests, use the following guide to identify the root cause. For deep inspection, open the Postman Console (Alt + Ctrl + C).

Error / Symptom	Probable Cause	Diagnostic Step
403 Signature Failed	Mismatch in SHA1 calculation.	Check for trailing spaces in your secretKey or if you are hashing the JSON body incorrectly.
404 Not Found	Incorrect endpoint URL.	Verify your {{baseUrl}} and ensure the API paths matches the standard (e.g., /sessions).
500 Internal Error	Unexpected exception.	Check your server logs. Usually caused by malformed database queries or null pointers.
Connection Timeout	Firewall / IP Blocking.	Ensure your server’s whitelist includes the IP from which you are running Postman.
Invalid Schema	Missing or renamed fields.	Compare your JSON response with the examples in the Standard Error Codes.

Advanced Debugging Tips

1. Check the Raw Request: Use the Postman Console to see the exact string being sent in the x-signature header.
2. Inspect Postman Scripts: If a variable is not being updated (e.g., walletSessionId), check the “Tests” tab of the previous request to see if the extraction logic failed.
3. Verify Header Case: Ensure headers like x-parent-system-id are being received correctly. Some frameworks modify the case of custom headers.

Certification & Support

Once you achieve a 100% Pass Rate in all suites:

1. Certification Request: Export your Postman Collection Run results as a JSON file.
2. Support Contact: If you cannot solve an error after reviewing the console, send the following to the GPAS support team:
   • Exported Collection + Environment (with sensitive data masked).
   • A screenshot of the Console showing the failing request/response.
   • A brief description of the steps to reproduce the error.

Danger

Warning: Never send your secretKey in plain text through support channels or email.