- Newest
- Most votes
- Most comments
The error MEMBER_IS_INVALID for the originationIdentity field usually occurs because the API expects a Sender ID or a Phone Number (E.164) associated with your RCS agent, rather than the Agent ARN itself.
Issues with your current command:
- ARN usage: The
--origination-identityparameter in thesend-text-messagecall often fails when provided with a full Resource ARN for RCS agents. - Parameter Mismatch: Contrary to some AI suggestions, there is no -
-rcs-agent-idparameter for thesend-text-messagecommand.
Option A: Use the Phone Number. Instead of the ARN, use the E.164 formatted phone number linked to your RCS setup:
--origination-identity "+49123456789"
Option B: Use the Message Configuration. Ensure the identity you are passing is registered as an "Origination Identity" in the AWS End User Messaging console under the same region (eu-central-1).
Option C: Verify IAM Permissions. Ensure your IAM policy explicitly allows sms-voice:SendTextMessage on the specific RCS Agent resource.
aws pinpoint-sms-voice-v2 send-text-message \
--destination-phone-number "+RECIPIENT_NUMBER" \
--origination-identity "YOUR_VERIFIED_ORIGINATION_NUMBER_OR_SENDER_ID" \
--message-body "Test message" \
--region eu-central-1
PS: If you are trying to send Rich Content (not just plain text), you should use the specific RCS-ready API actions or ensure your Origination Identity is part of a pool that supports RCS capabilities.
Based on the error you're encountering, the issue is likely related to how you're specifying the origination identity parameter for RCS testing. Here are the key points to address:
Parameter Usage for RCS Testing:
When testing RCS messages, the --origination-identity parameter and --rcs-agent-id parameter are mutually exclusive. For RCS testing specifically, you should use --rcs-agent-id instead of --origination-identity. The --origination-identity parameter is used for SMS verification (sending OTP SMS), while --rcs-agent-id is used to register phone numbers for RCS testing with that agent.
Corrected Approach:
Try modifying your CLI command to use the --rcs-agent-id parameter:
aws pinpoint-sms-voice-v2 send-text-message \ --destination-phone-number "+PHONE_NUMBER" \ --rcs-agent-id "AGENT-ID" \ --message-body "Test message" \ --message-type "TRANSACTIONAL" \ --region eu-central-1
Note that when using --rcs-agent-id, you should specify just the agent ID, not the full ARN.
Alternative:
If you want to use the --origination-identity parameter, it should be used without the --rcs-agent-id parameter, but this would be for SMS verification purposes rather than RCS testing.
Since your RCS agent is already in "Testing and Active" status and your test device is verified, switching to the correct parameter should resolve the INVALID_PARAMETER error you're experiencing.
Sources
Testing RCS messages - AWS End User Messaging SMS
using --rcs-agent-id creates the following error
aws: [ERROR]: Unknown options: --rcs-agent-id,
Thanks for the feedback. Maybe I am missing something but using a phone number or senderID as origination_identity will send the message as SMS only. This I am able to do.
My intention is to test the new RCS setup. And here also the RCS testing interface fails with an error when trying to send the test message.
Validation Error Occurred - Reason="INVALID_PARAMETER" Fields="originationIdentity" [originationIdentity: MEMBER_IS_INVALID] RequestId: 3a1a4654-43df-4d16-8206-1459e8e3f9cf HttpStatusCode: 400
Hi Thilo, thanks for clarifying. Since the console also throws the MEMBER_IS_INVALID error for originationIdentity , it indicates that the identity you are using isn't recognized as an RCS-enabled member of your configuration, even if it works for SMS.
What you can may check again.
Pool Association: Ensure your origination phone number is explicitly associated with a Pool. In the AWS End User Messaging console, verify that this Pool has RCS capabilities enabled. If the number is used standalone, the API often defaults to the SMS workflow.
API Action: If you are using the CLI for RCS specifically, ensure you are testing with a plain text string first, as complex payloads in send-text-message can sometimes trigger validation errors on the origination identity if the content doesn't match the identity's capabilities.
Hi Florian, thanks again. Maybe we scale this back even more. Generally End User Messaging with Phone Number, SenderID and Phone Pools work smoothly. In a first step I just want to get the RCS testing running. I assume that I have everything for this in place:
If I then go the AWS End User Messaging console -> RCS agents, select my agent and then try within the testing section to send a test message this already fails with this error: Reason="INVALID_PARAMETER" Fields="originationIdentity" [originationIdentity: MEMBER_IS_INVALID] And all my attempts only contained plain text.