Log inTry for free
Back to all APIs

Create an RCS sender Early access

Create an RCS sender. Created RCS sender can immediately be used to send test messages to test numbers. See Add RCS test number operation for more details about adding test numbers for sender. Please note that following limits will apply when creating RCS sender:

  • It is allowed to add up to 10 senders in total.

Please contact your account manager if you need to add more senders.

Please log in to see full path URL. Learn why.
post
/rcs/1/senders
Authorizations:
API Key Header
Basic
IBSSO Token Header
OAuth 2
Scopes:
rcs:manage
Request rate limit:
1 requests / second (per account)
Request Body schema:
application/json
collapse all -
senderName
required
string [ 3 .. 40 ] characters ^(?=.*[a-zA-Z])[a-zA-Z0-9_-]+$

Unique identifier of Sender entity for RCS channel within Infobip platform. It must be provided when submitting RCS traffic to Infobip platform. It must contain only alphanumeric characters, underscores and hyphens, and must contain at least one letter. It's not editable at any point of time after sender is created.

billingCategory
required
string
Enum: "BASIC_MESSAGE" "SINGLE_MESSAGE" "CONVERSATIONAL"

Billing category for the sender. Following billing categories are available:

  • BASIC_MESSAGE: Messages billed based on message length similar to SMS. Never billed as CONVERSATIONAL.
  • SINGLE_MESSAGE: Messages billed as standard RCS message that allows richer messaging experience. Never billed as CONVERSATIONAL.
  • CONVERSATIONAL: Billed as session in which user and agent can exchange a series of messages.
useCase
required
string
Enum: "OTP" "TRANSACTIONAL" "PROMOTIONAL" "MULTI_USE"

Use case for the sender. Following use cases are available:

  • OTP: Used for senders that only send one time passwords.
  • TRANSACTIONAL: Used for senders that send only essential, necessary and time-sensitive messages.
  • PROMOTIONAL: Used for senders that send promotional messages.
  • MULTI_USE: Used for senders that have multiple use cases.
brand
required
object

Brand for which sender is created.

brandName
required
string [ 1 .. 100 ] characters

Name of the brand.

displayName
required
string [ 1 .. 100 ] characters

The name of the sender displayed to the user on mobile device.

description
required
string [ 1 .. 100 ] characters

The description of the sender displayed to the user on mobile device.

color
required
string ^#?([A-Fa-f0-9]{6})$

Theme color of the sender that is visible to the user on mobile device. Must be in hex format and contrast ratio must be at least 4.5:1 for white.

phone
object

Phone contact associated with the sender and displayed to the user on mobile device. Required if email contact not defined.

phoneNumber
required
string ^\+?[1-9]\d{1,14}$

Phone number. It must be in E.164 format, e.g. +1234567890. Leading '+' is optional.

label
required
string [ 1 .. 25 ] characters

Label for the phone number.

email
object

Email contact associated with the sender and displayed to the user on mobile device. Required if phone contact not defined.

address
required
string [ 0 .. 100 ] characters

Email address. Must be in valid email format.

label
required
string [ 1 .. 25 ] characters

Label for the email address.

website
required
object

Website associated with the sender and displayed to the user on mobile device.

url
required
string

A publicly accessible URI associated with the sender. Must use the HTTP or HTTPS protocol.

label
required
string [ 1 .. 25 ] characters

Label for the URI.

bannerUrl
required
string

URL of the banner image associated with the sender and displayed to the user on mobile device. It must be in JPG / JPEG or PNG format and it must be in 1440 x 448 resolution (width x height).

logoUrl
required
string

URL of the logo image associated with the sender and displayed to the user on mobile device. It must be in JPG / JPEG or PNG format and it must be in 224 x 224 resolution (width x height).

privacy
required
object

Privacy policy associated with the sender.

url
required
string

A publicly accessible URI associated with the sender. Must use the HTTP or HTTPS protocol.

label
required
string [ 1 .. 25 ] characters

Label for the URI.

termsOfService
required
object

Terms and conditions associated with the sender.

url
required
string

A publicly accessible URI associated with the sender. Must use the HTTP or HTTPS protocol.

label
required
string [ 1 .. 25 ] characters

Label for the URI.

platform
object

Platform parameters that would be associated with the sender. Please note that platform parameters must be created before they can be associated with the sender. For more details, see documentation.

applicationId
string [ 0 .. 255 ] characters

ID of the Application that would be associated with the sender.

entityId
string [ 0 .. 255 ] characters

ID of the Entity that would be associated with the sender.

Responses

202

Request has been accepted and result of create sender operation will be sent to webhook

400

Bad request

401

Unauthorized

403

Forbidden

409

Conflict

429

Too Many Requests

500

Internal Server Error

Request samples

Content type
application/json
Copy
 Collapse all
{}

Response samples

Content type
application/json
Copy
 Collapse all
{
  • "senderName": "DemoSender",
  • "requestStatus": "PENDING"
}

Need assistance

Explore Infobip Tutorials

Encountering issues

Contact our support

What's new? Check out

Release Notes

Unsure about a term? See

Glossary

Research panel

Help shape the future of our products
Learn more
Service status

Copyright @ 2006-2025 Infobip ltd.

Privacy documentsTerms of use