Test and go live

Live keys sell real policies. Before they work, your business must be verified, finish the activation checklist in test, and be approved for production by NetApps InsureTech.

1. Finish the activation checklistlink

The Production activation card on Integration ticks each step the first time it succeeds with a test key. A step never un-ticks, and a replayed request does not count.

StepHow to tick it
A quote fetched in test modePOST /quotes with a test key. A 202 pending quote counts too.
A purchase completed in test modePOST /purchases with a test key.
A webhook delivered to a test endpointA 2xx answer to any test event, or to POST /webhook-endpoints/{endpointId}/test with a test key.

2. Request production accesslink

When your business is verified and every step is ticked, the owner chooses Request production activation. If something is missing, the message lists it.

BadgeMeaning
PendingNetApps InsureTech is reviewing your request.
ApprovedLive keys work.
RejectedThe reason is shown. Fix it and request again.
SuspendedEvery key, test and live, is refused with 403 BUSINESS_SUSPENDED until your business is reinstated.

The owner is emailed at every decision.

3. Create a live keylink

Switch the dashboard to live mode, open API Keys and create a key, exactly as for a test key. You can create a live key once your business is verified, but it answers 403 PRODUCTION_NOT_ACTIVATED until production access is approved.

4. Switch your server to livelink

  • Store the live key in your server's secret store, next to the test key, and pick one by environment.
  • Register your webhook endpoint again with the live key. Test endpoints never receive live events.
  • Store the live endpoint's signing secret.
  • Charge real payments with your processor's live account.
  • Reconcile your first live statement against your own orders.

Before your first real salelink

  • You handle 202 pending quotes and QUOTE_PENDING.
  • You treat an unknown purchase status as "not issued yet".
  • You refund your customer on purchase.failed.
  • You verify every webhook signature and ignore repeated eventIds.
  • You send a fresh Idempotency-Key per write and reuse it only to retry that write.
  • You log X-Request-Id on every call, to quote to support.