Test mode and API keys
Updated 2026-09-07
On this page
Test mode keeps integration work off production carriers and live Stripe charges. Stay in test until create-order → rates → buy → void is green.
How to stay in test
- Create and use keys that start with
nm_test_ - In MCP OAuth consent, choose Test (default)
- Point webhooks at a staging HTTPS URL while validating payloads
- Prefer
Idempotency-Keyon creates so retries are safe
What differs in test
- Carrier rating / purchase uses test pathways for your environment
- Mistakes should not consume live postage (still void test labels when created)
- Webhook deliveries still need a reachable HTTPS endpoint
Promote to live checklist
- Finish the quickstart scripts on test keys.
- Attach a Billing payment method for platform postage.
- Create
nm_live_keys and store them in a secrets manager. - Re-register webhooks for production URLs.
- Buy one cheap live label, void if unused, then cut over traffic.
- Revoke unused test keys if they leave staging.
Important
nm_live_ buys real labels. Protect live keys like production database passwords.
MCP note
Call nm_me and confirm key_environment is test before nm_buy_label. See MCP.