404
testkit.not_in_livetestkitRule R1Rule R3Test-data operations are refused in live mode
ResetTestData and PurgeTestData delete data. In live mode they refuse and delete nothing — and they answer 404 rather than 403, so that a live key cannot even confirm the operation exists.
Why the API refuses
WHEN ResetTestData or PurgeTestData is executed while the caller's effective mode is live, THE SYSTEM SHALL refuse with testkit.not_in_live and delete nothing.
WHEN any test-mode kit operation is executed while the caller's effective mode is live, THE SYSTEM SHALL refuse with testkit.not_in_live, change nothing and record the refusal in the audit trail.
What to do
Use a pg_test_ key. If a live key reached this call, the more urgent question is why your deployment is pointing test tooling at live credentials.
Operations that can return it
- testkit.AdvanceClock
- testkit.CreateWebhookSink
- testkit.DeleteWebhookSink
- testkit.GetWebhookSink
- testkit.ListSinkDeliveries
- testkit.ListTestkitActions
- testkit.ListWebhookSinks
- testkit.PurgeTestData
- testkit.SeedTestData
- testkit.SimulatePayment
- testkit.SimulatePayout
- testkit.SimulateRefund
- testkit.SimulateSettlement
- testkit.UpdateWebhookSink