Documentation

Testing

Simulate messages and verifications to test your integration.

Test your integration by simulating transactions with test values—these transactions don’t move real messages or charges.

Don't use real data

Don’t use real phone numbers or emails for testing. Use our provided test values below to avoid triggering real-world side effects.

How to use test values

When you work with a test API key, use test phone numbers in all API calls. This is true whether you’re sending a message or creating a verification.

Messaging test numbers

When testing messaging, use a number such as +1 234 567 8900.

  • Use a valid future date if required.
  • Use any alphanumeric string for message content.

Verification test codes

When writing test code, use 123456 as the OTP code. By default, any other code will result in a validation error in the test environment.

Simulate different outcomes

You can simulate specific API responses by using designated test values.

ValueExpected Outcome
+1 000 000 0000Success (Delivered)
+1 000 000 0001Permanent Failure
+1 000 000 0002Temporary Failure (Retry)

Rate limits in test mode

The test environment has lower rate limits than production. If you need to load test your integration, please contact support to enable a dedicated sandbox.