Sinch RCS Senders API

Manage RCS sender identities for Rich Communication Services messaging through the Conversation API.

Operations 6

GET /v1/projects/{project_id}/rcs/senders List Rcs Senders #
POST /v1/projects/{project_id}/rcs/senders Create an Rcs Sender #
GET /v1/projects/{project_id}/rcs/senders/{sender_id} Get an Rcs Sender #
PATCH /v1/projects/{project_id}/rcs/senders/{sender_id} Update an Rcs Sender #
DELETE /v1/projects/{project_id}/rcs/senders/{sender_id} Delete an Rcs Sender #
POST /v1/projects/{project_id}/rcs/senders/{sender_id}/launch Launch an Rcs Sender #

Documentation

Specifications

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/sinch-rcs-senders-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

sinch-rcs-senders-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Sinch Provisioning RCS Senders API
  description: The Sinch Provisioning API allows developers to programmatically set up senders, accounts, and templates on the messaging platforms used by the Sinch Conversation API. It provides endpoints for configuring messaging channel integrations, managing sender identities, and setting up message templates for approval. This API streamlines the onboarding process for new messaging channels and automates the configuration that would otherwise require manual setup through dashboards.
  version: '1.0'
  contact:
    name: Sinch Support
    url: https://www.sinch.com/contact-us/
  termsOfService: https://www.sinch.com/terms-of-service/
servers:
- url: https://provisioning.api.sinch.com
  description: Global Production Server
security:
- oAuth2: []
- basicAuth: []
tags:
- name: RCS Senders
  description: Manage RCS sender identities for Rich Communication Services messaging through the Conversation API.
paths:
  /v1/projects/{project_id}/rcs/senders:
    get:
      operationId: listRcsSenders
      summary: List Rcs Senders
      description: Returns a list of all RCS senders configured for the project.
      tags:
      - RCS Senders
      parameters:
      - $ref: '#/components/parameters/ProjectId'
      responses:
        '200':
          description: List of RCS senders
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RcsSenderList'
        '401':
          description: Unauthorized
    post:
      operationId: createRcsSender
      summary: Create an Rcs Sender
      description: Creates a new RCS sender identity with brand information and messaging agent configuration.
      tags:
      - RCS Senders
      parameters:
      - $ref: '#/components/parameters/ProjectId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateRcsSenderRequest'
      responses:
        '200':
          description: RCS sender created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RcsSender'
        '400':
          description: Invalid request
        '401':
          description: Unauthorized
  /v1/projects/{project_id}/rcs/senders/{sender_id}:
    get:
      operationId: getRcsSender
      summary: Get an Rcs Sender
      description: Returns the details and status of a specific RCS sender.
      tags:
      - RCS Senders
      parameters:
      - $ref: '#/components/parameters/ProjectId'
      - $ref: '#/components/parameters/SenderId'
      responses:
        '200':
          description: RCS sender details
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RcsSender'
        '401':
          description: Unauthorized
        '404':
          description: Sender not found
    patch:
      operationId: updateRcsSender
      summary: Update an Rcs Sender
      description: Updates the configuration of a specific RCS sender.
      tags:
      - RCS Senders
      parameters:
      - $ref: '#/components/parameters/ProjectId'
      - $ref: '#/components/parameters/SenderId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateRcsSenderRequest'
      responses:
        '200':
          description: RCS sender updated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RcsSender'
        '401':
          description: Unauthorized
        '404':
          description: Sender not found
    delete:
      operationId: deleteRcsSender
      summary: Delete an Rcs Sender
      description: Deletes a specific RCS sender from the project.
      tags:
      - RCS Senders
      parameters:
      - $ref: '#/components/parameters/ProjectId'
      - $ref: '#/components/parameters/SenderId'
      responses:
        '200':
          description: RCS sender deleted
        '401':
          description: Unauthorized
        '404':
          description: Sender not found
  /v1/projects/{project_id}/rcs/senders/{sender_id}/launch:
    post:
      operationId: launchRcsSender
      summary: Launch an Rcs Sender
      description: Submits an RCS sender for launch, initiating the approval process with carriers and Google.
      tags:
      - RCS Senders
      parameters:
      - $ref: '#/components/parameters/ProjectId'
      - $ref: '#/components/parameters/SenderId'
      responses:
        '200':
          description: RCS sender launch initiated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RcsSender'
        '401':
          description: Unauthorized
        '404':
          description: Sender not found
components:
  schemas:
    RcsSender:
      type: object
      properties:
        id:
          type: string
          description: The unique sender identifier
        displayName:
          type: string
          description: The display name shown to recipients
        description:
          type: string
          description: The sender description
        logoUrl:
          type: string
          format: uri
          description: URL to the sender logo
        heroImageUrl:
          type: string
          format: uri
          description: URL to the hero image
        phoneNumber:
          type: string
          description: The associated phone number
        color:
          type: string
          description: Brand color in hex format
        website:
          type: string
          format: uri
          description: Brand website URL
        privacyPolicy:
          type: string
          format: uri
          description: Privacy policy URL
        termsOfService:
          type: string
          format: uri
          description: Terms of service URL
        status:
          type: string
          description: The current sender status
        createTime:
          type: string
          format: date-time
          description: When the sender was created
        updateTime:
          type: string
          format: date-time
          description: When the sender was last updated
    CreateRcsSenderRequest:
      type: object
      required:
      - displayName
      properties:
        displayName:
          type: string
          description: The display name
        description:
          type: string
          description: The sender description
        logoUrl:
          type: string
          format: uri
          description: Logo URL
        heroImageUrl:
          type: string
          format: uri
          description: Hero image URL
        phoneNumber:
          type: string
          description: Associated phone number
        color:
          type: string
          description: Brand color
        website:
          type: string
          format: uri
          description: Website URL
        privacyPolicy:
          type: string
          format: uri
          description: Privacy policy URL
        termsOfService:
          type: string
          format: uri
          description: Terms of service URL
    UpdateRcsSenderRequest:
      type: object
      properties:
        displayName:
          type: string
          description: Updated display name
        description:
          type: string
          description: Updated description
        logoUrl:
          type: string
          format: uri
          description: Updated logo URL
        heroImageUrl:
          type: string
          format: uri
          description: Updated hero image URL
    RcsSenderList:
      type: object
      properties:
        senders:
          type: array
          description: List of RCS senders
          items:
            $ref: '#/components/schemas/RcsSender'
  parameters:
    ProjectId:
      name: project_id
      in: path
      required: true
      description: The unique project identifier
      schema:
        type: string
    SenderId:
      name: sender_id
      in: path
      required: true
      description: The unique sender identifier
      schema:
        type: string
  securitySchemes:
    oAuth2:
      type: oauth2
      description: OAuth 2.0 client credentials flow.
      flows:
        clientCredentials:
          tokenUrl: https://auth.sinch.com/oauth2/token
          scopes: {}
    basicAuth:
      type: http
      scheme: basic
      description: Key ID as username and key secret as password.
externalDocs:
  description: Sinch Provisioning API Documentation
  url: https://developers.sinch.com/docs/provisioning-api