We have encountered an issues connecting to the GP Connect API (Spine INT), since the 23rd Dec.
502 transient Error communicating to target URL
Here is the request
Any suggestions on the cause?
Now resolved this can be closed.
Glad that you have been able to resolve the issue.
Adding some addition info for community users who may face similar issues:
A 502 (“Bad Gateway”) from Spine typically indicates that your request reached the Spine endpoint (or an intermediate proxy) but then Spine/Spine INT could not retrieve a valid response from the internal service.
For users facing similar issues - we would recommend the inclusion of full request/response logs to spot any more detailed error information in the response body.
Also consider checking the Spine INT environment’s status for that period and review logs for more specific error messages. Ensure you are sending all required Spine headers and that the JWT in the Authorization header is valid and includes the correct SDS role profiles.
Users with similar errors should also consider verifying your configuration (headers, endpoint, certificates), and if the problem continues, contact NHS Digital’s GP Connect/Spine INT support to check for environment-specific issues.