50341: Invalid messaging service SID

You supplied MessagingServiceSid with a value that does not identify a valid Messaging Service. Use a Messaging Service SID only in requests that accept MessagingServiceSid, and make sure it matches the required MG SID format.

• The MessagingServiceSid value does not match the required pattern. A valid Messaging Service SID starts with MG and is followed by 32 hexadecimal characters.
• You passed a SID from a different resource type, such as IS, CH, AC, or SM, instead of a Messaging Service SID. Twilio uses resource-specific SID prefixes, and MessagingServiceSid only accepts an MG SID.
• The SID was truncated, copied with extra characters or whitespace, or otherwise changed so it no longer matches the exact service SID returned by the Console or API.
• If you are migrating a Programmable Chat channel, you included MessagingServiceSid in the migration request but used a value that is not a valid Messaging Service for that request.

• Copy the Messaging Service SID directly from Messaging > Services in Console, or retrieve it from the Messaging Services API, then resend the request with the exact value.
• Validate MessagingServiceSid before you send the request. It must be exactly 34 characters long and match ^MG[0-9a-fA-F]{32}$.
• Do not use an Account, Chat Service, Channel, or Message SID in the MessagingServiceSid field. Send only the MG SID for the Messaging Service you want to use.
• If you are migrating a Chat channel so you can add SMS or WhatsApp participants in Conversations (classic), create or identify the correct Messaging Service first, then include that MessagingServiceSid in the migration request.

• Chat Channel Migration Resource
• Migrating to Conversations (classic) from Programmable Chat
• Messaging Services