Pega Infinity ’26 – Connect Agent to External A2A Agent Returns HTTP 422

Hi everyone,
I am working on Pega Infinity ’26 and trying to invoke an external A2A (Agent-to-Agent) agent using a Connect Agent rule.
Setup:
Pega Infinity ’26 Trial environment
External A2A agent configured with an Agent Card URL
Connect Agent rule configured with the external Agent Card URL
Authentication configured using OAuth 2.0 Client Credentials
OAuth authentication is working correctly.
The same API request has been tested successfully using Postman, where I receive an HTTP 200 response.
Issue:
When I invoke the same external agent through the Connect Agent rule in Pega, the request fails with:
HTTP Response Code: 422 – Unprocessable Entity
The Tracer indicates that the response data may contain the reason for the failure.
In the Pega UI, the response message displayed to the user is:
“I’m sorry, I wasn’t able to retrieve the risk assessment for this payment change request at the moment due to a technical issue. Please try again shortly, or contact support if the problem persists.”
Expected Behavior:
I expect the Connect Agent invocation to receive the same successful response (HTTP 200) that I receive when testing the API through Postman.
Question:
Could someone please help me understand what could cause a 422 response when invoking the external A2A agent through Connect Agent, while the same request works successfully from Postman?

Are there any specific A2A request/response format, Agent Card, headers, content type, JSON structure, or Connect Agent configuration requirements that I should verify in Pega Infinity ’26?

Thanks in advance for your help!

Could you please confirm if you can try the same request which is failing through A2A in Postman?

Hi everyone,

I was able to identify the issue. It appears to be a request payload format mismatch between Pega Connect Agent and the external A2A agent.

Thank you!