Integrating a messaging API used to mean sending yourself forty text messages and paying for each one. Every SMSMeteor account has a test key, prefixed sk_test_, next to its live keys, and it can be used before any deposit.
What a test request does
Everything except the last step. The number is normalised to E.164, the destination resolved, the sender rule applied, the text encoded and segmented, the price computed from the live rate card. The response is the real response, with "status": "test". Nothing is handed to a carrier and nothing is debited from your balance.
Because validation is real, a test key catches the errors that matter during integration: numbers without country codes, destinations that are not routed, texts that are longer than you thought, and senders that will be replaced on some routes. The segments and price fields tell you what a live send would cost.
Webhooks too
Test messages emit webhooks to your endpoints, signed exactly like live ones. Your handler can be built and verified end to end: signature check, deduplication, status updates in your database. The quickstart walks through the whole loop in five minutes.
What it cannot tell you
A test key does not tell you whether a real message will be delivered, how fast, or under which sender it will appear on the handset; only a carrier can. It also does not exercise your balance logic, since nothing is debited.
Going live
- Create a live key with the narrowest scope you need:
sendfor the service that sends,readfor dashboards. - Restrict the key to your servers' IP addresses where possible; requests from other addresses are refused.
- Fund the balance with a small deposit.
- Send one real message to your own phone and check three things: the arrival, the sender shown, and the
message.deliveredwebhook in your database. - Switch the production configuration to the live key.
Key hygiene
- Use separate keys per environment and per service, so revoking one does not stop everything.
- Keep keys in environment variables or a secret manager, never in front-end code or a repository.
- Rotate a key immediately if it appears in a log, a ticket or a screenshot.
- Use an Idempotency-Key on every send, test or live, so retries never double-send.


