---
title: "Add RCS test number"
method: POST
path: "/rcs/1/senders/{senderName}/test-numbers"
tags: ["channels", "rcs", "rcs-service-management", "rcs-test-number-management"]
---

# Add RCS test number

`POST /rcs/1/senders/{senderName}/test-numbers`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/rcs/1/senders/{senderName}/test-numbers`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

Add test number for given RCS sender. Invitation to become tester will be sent to given number and once user accepts invitation it will be possible to send test traffic to given test number using given sender. Please note that following limits will apply when adding test number for RCS sender:
* It is allowed to add up to 20 test numbers per sender per day.
* It is allowed to add up to 200 test number per sender in total.

## Path parameters

- `senderName` string, required

## Request body

- C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913CreateRcsTestNumberApiRequest
  - `testNumber` string, required: Full number in E.164 format, e.g. +1234567890. Leading '+' is optional.
  - `primary` boolean: Set this test number as primary for this sender. A test number can only be primary for one sender, although a sender may have multiple numbers marked as primary; selecting it here will remove the primary flag from any sender where it is already marked as such. Relevant when multiple senders share the same Application and Entity via Resource Association.

## Response `202`

Request has been accepted and result of add test number operation will be sent to webhook

- C4d4776b979fea48176211c392051aca0dae21d75b7a9ca349c8f2eb95a84913RcsTestNumberRequestAcceptedResponse
  - `senderName` string, required: Unique identifier of a sender for which test number is associated.
  - `testNumber` string, required: Full number in E.164 format, e.g. +1234567890. Leading '+' is optional.
  - `status` 'PENDING' | 'WAITING_FOR_TESTER_ACCEPTANCE' | 'APPROVED' | 'EXPIRED' | 'UNSUPPORTED' | 'FAILED', required: Status of the test number. It'll be updated by Infobip platform automatically and notification about test number status update will be sent to client's webhook. Following statuses are available: * `PENDING`: Test device registration is pending until 3rd party action will be executed. * `WAITING_FOR_TESTER_ACCEPTANCE`: Waiting for user to accept request to become a tester. * `APPROVED`: User has accepted to become a tester and test messages can be sent to that number. * `EXPIRED`: If user does not accept invitation within 24h, status of test number will be moved to EXPIRED. * `UNSUPPORTED`: Test number is not supported for RCS traffic. * `FAILED`: Failed mostly because of some internal service error during request processing. Please contact support.

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `409`: Conflict
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)