Spring Boot service keeps throwing a 422 Unprocessable Entity on /api/v2/conversations/messaging/{conversationId}/participants. The Java SDK version is 2024.9.0. Documentation clearly states: “When creating a messaging conversation participant, the to address must match a supported messaging channel format.” Payload is passing a valid E.164 number wrapped in the proper Address object. Console logs show the JSON matches the schema exactly. Thread pool is configured for 20 connections, so it’s not a timeout issue. The request hits the endpoint, GC validates it, and immediately rejects it with a field_validation_error on the to field.
Environment specs:
- Java 17, Spring Boot 3.2.1
- Genesys Cloud Java SDK 2024.9.0
- Region: eu-2
- Message type: SMS via BYOC
Platform docs also mention: “For SMS participants, the to address must be a fully qualified E.164 number without prefixes.” Stripped the plus sign, tried with it, swapped to sms: prefix. Nothing changes. The SDK builder method createConversationParticipantRequest silently drops the type field if you don’t explicitly set it to SMS, but the payload still fails validation. Why is the endpoint rejecting a structurally correct request when the docs guarantee this format works? Doing jack all with the current retry logic. Error trace just points to HttpClientErrorException.