Skip to main content
POST
/
transactional_messages
/
send_rcs_file
Send an RCS File
curl --request POST \
  --url https://api.v3.tatango.com/transactional_messages/send_rcs_file \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "phoneNumber": "5551234567",
  "webhookUrl": "https://api.example.com/webhooks/rcs",
  "rcsPayload": {
    "file": {
      "url": "https://example.com/files/weekly-news-letter.pdf"
    }
  },
  "smsFailover": "Check out our latest newsletter! https://example.com/weekly-news-letter.pdf"
}
'
{
  "message": "RCS file message sent successfully",
  "transactionId": "019687e1-1b54-70f4-a68a-60af7fa776f4"
}

Documentation Index

Fetch the complete documentation index at: https://platform.tatango.com/llms.txt

Use this file to discover all available pages before exploring further.

RCS File messages allow you to send file attachments with optional action buttons for enhanced user interaction.RCS File Features:
  • File Support: Send various file types as attachments, notably PDF and audio files
  • Rich Experience: Enhanced file sharing with interactive elements
  • Fallback: Automatic SMS fallback if RCS delivery fails
Requirements: Valid U.S. phone number with RCS support

Authorizations

​
x-api-key
string
header
required

Your Tatango API key. This is required for all requests to the API. You can find your API key in the Tatango App under My Account -> API -> Create API Key.

Body

application/json

The RCS File message request with SMS fallback.

​
phoneNumber
string
required

The destination phone number. Can be provided in any format (e.g., +1 555-123-4567, (555) 123-4567, 5551234567) but must be a valid U.S. or Canadian phone number.

​
webhookUrl
string
required

URL where webhooks will be sent. Must be a valid HTTPS URL.

Maximum string length: 255
​
rcsPayload
object
required
​
smsFailover
string
required

SMS fallback message content used when primary delivery method fails. Must contain only GSM 7-bit characters.

Required string length: 1 - 160

Response

RCS File message accepted.

​
message
string
required

Success message indicating the request was accepted.

​
transactionId
string
required

Unique transaction identifier for tracking the message.