Skip to main content

test_mode_restricted

You authenticated with a tix_test_ key on an operation reserved for live keys. Nothing was created, nothing was sent, and no quota was used.

Status: 403

{
  "status": 403,
  "type": "test_mode_restricted",
  "message": "A test API key can only create other test API keys",
  "request_id": "req_01J8K2P...",
  "doc_url": "https://docs.epostix.com/errors/test_mode_restricted"
}

Why you got this​

  • You asked a test key to create a live key. A test key may only create other test keys.
  • You tried an inbound endpoint or a broadcast send/test operation with a test key.
  • The environment your code runs in is configured with the test key where the live key was meant to be.
  • The key was copied out of the wrong environment. The prefix tells you which one you have: tix_test_ or tix_live_.

How to fix it​

Check the prefix of the key you sent. The two environments are not interchangeable, and the prefix has to match the environment you are working in. Repeat the call with a tix_live_ key, or perform the operation from the dashboard.

Test keys also cannot read inbound mail or send or test broadcasts. Other management resources are still workspace resources, not isolated test copies. Simulated sends do not deliver real mail or consume sending quota. Rate limits for test traffic are counted separately from live traffic. See test mode for what a test key can do and how the simulated recipients at epostix.dev behave.

Is it safe to retry​

No, not with the same key. The same test key is refused every time. Send the request again with a live key.

The live API key has a separate idempotency scope. A send with it can deliver real mail, even if the same idempotency key was used for a simulated send.