RCS Scenario
This request starts an RCS scenario for a list of numbers from its identifier (token).
Overview
An RCS scenario is an automated dialogue configured on the platform: an entry message, clickable suggestions, and bot replies depending on the recipient's choices.
This route starts a scenario for a list of numbers by simply providing its identifier (scenarioToken), without having to rebuild its content. Once the entry message has been sent, the rest of the dialogue (bot replies to clicks) is handled automatically by the platform.
The identifier can also be pasted into our modules and connectors (PrestaShop, WooCommerce, Zapier, Make…) wherever an “RCS scenario identifier” is requested.
The identifier is available in RCS Scenarios (/dashboard/rcs/scenario), “API Identifier” column, Copy identifier button.
URL
POST https://api.smspartner.fr/v1/rcs/scenario/to/send
Rate limit: 30 requests / 60 seconds (see Rate limiting))
The platform does not send commercial SMS messages between 8 PM and 8 AM on weekdays and on Sundays and public holidays (legal restriction). If a commercial SMS is sent, the message is paused until the next working day at 8 AM. Not sending commercial SMS messages? Contact us to disable this restriction: help@smspartner.fr
Required Parameters
apiKey
scenarioToken
Identifier of the RCS scenario to start. The scenario must be validated / activated on the platform.
phoneNumbers
Recipient phone numbers. To send to multiple recipients, the numbers must be separated by commas. The limit per request is 500 numbers. They can be:
in national format (06xxxxxxxx) or international format (+336xxxxxxxx), for French numbers.
in international format (+496xxxxxxxx), for non-French numbers.
Optional Parameters
sender
Sender of the fallback SMS (failover).
tag
Free label to find the send later (3 to 20 characters, no spaces).
scheduledDeliveryDate
Send date in dd/mm/YYYY format (scheduled send).
time
Send time (0-24 format).
If scheduledDeliveryDate is set, this parameter is required.
minute
Send minute (0-55 format, in five-minute intervals).
If scheduledDeliveryDate is set, this parameter is required.
scheduledAt
Scheduled send as a single value: absolute date (2026-05-20 10:15, 20/05/2026 10:15, ISO 8601…) or relative delay (+2 hours, +3 days…). Replaces scheduledDeliveryDate / time / minute. The resulting date must be in the future and at most 3 months ahead.
sandbox
true = simulation, no real send.
urlDlr
Callback URL for delivery receipts.
urlResponse
Callback URL for replies / interactions.
failover
Fallback SMS if the RCS is not delivered: { "message": "...", "sender": "..." }.
Requests
Example with SMS fallback and scheduling
What happens next
The scenario's entry message is sent to the provided numbers.
When a recipient clicks a suggestion, the RCS webhook automatically triggers the send of the next node of the scenario.
Response
Errors
Error codes
1
The API key is required
2
phoneNumbers is required
13
No default price to this destination
14
Number in the STOP list
50
scenarioToken is required (missing parameter)
55
No valid number to send to
63
RCS scenario not found: the token does not match any scenario in your account
64
The RCS scenario is not activated: the scenario exists but has not been validated / activated on the platform
65
The RCS scenario has no entry message / is empty: no valid first node (complete it on the platform)
96
IP not allowed
401
Account not authorized for RCS
403
User not authorized (invalid API key, disabled account…)
All other validations (numbers, scheduling, field sizes, credits…) are identical to a standard RCS send.
Last updated