Articles on: API Services

Sandbox environment

The sandbox allows you to test inbound and outbound messages without using your credits or purchasing a dedicated sender name. You can use this feature to test the API before using it on Production.

Messages sent within the Sandbox will always contain technical information at the end of each message.

The sandbox is designed to help your developers or QA team not use the main request limit for which you pay. This also will help you solve the issue when need to send messages separately only for testing and separately use them in a production environment.
To use the sandbox, you need to add a phone number or email as a sandbox contact in the Dashboard -> Conversation API -> Settings, then initiate a conversation with the sandbox sender name by pressing Compose message in sandbox from your Mac or iPhone.
You must set a phone number or email that you set up as Start new conversation from in the Messages app. Check this article to learn more about this setting.
In this case, all your requests for this contact will be force marked as the sandbox. Sandbox works only with one-to-one messaging. With group chats, this feature may be unstable.

Keep in mind that when your implementation is used in a production environment, remember to remove the specified contact from the sandbox list, otherwise all requests related to this contact will continue to be processed as a sandbox.

Don't use sandbox messaging in a production environment. If you will abuse it, we reserve the right to nullify your sandbox limit.

It is strongly recommended that you first start a conversation, and only then reply to a message from the sandbox. This way you will be able to reproduce the full cycle of 2-way conversation as it would be in a production environment. If you successfully sent an outbound message first without receiving an inbound message before, this does not mean that it will work exactly the same in a production environment.

Updated on: 21/04/2023

Was this article helpful?

Share your feedback


Thank you!