---
title: "Go-Live Checklist"
description: "Move a SignatureAPI integration from test to live mode: live keys, live webhooks and senders, retries, failure alerts and a data retention plan."
canonical: "https://signatureapi.com/docs/api/guides/go-live-checklist"
source: "https://signatureapi.com/docs/api/guides/go-live-checklist.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T17:35:44Z"
---

# Go-Live Checklist

Move a SignatureAPI integration from test to live mode: live keys, live webhooks and senders, retries, failure alerts and a data retention plan.

_Last verified against API version 1.18.0._

Test and live mode run the same API, so going live is mostly configuration. Live mode has its own envelopes, webhook endpoints and senders, which means everything you set up in test mode needs a live twin. Work through this list before your first live envelope.

## Checklist

**Go-live checklist**

- [ ] [Create a live API key](https://signatureapi.com/docs/api/test-mode#switch-to-live-mode): Live keys start with `key_live_`. Replace `key_test_` with it in your API calls; no other code changes are needed.
- [ ] [Keep the API key on your server](https://signatureapi.com/docs/embedded/introduction#client-side): Never call the API from the client: anyone with your key can access all your data in SignatureAPI.
- [ ] [Register webhook endpoints for live mode](https://signatureapi.com/docs/api/webhooks): Test and live mode are independent: live events go only to live endpoints, and test envelopes, webhooks and senders are separate from live ones.
- [ ] [Verify webhook signatures](https://signatureapi.com/docs/api/webhooks#authentication): Check the HMAC signature in the `webhook-signature` header with the endpoint's signing secret, following the Standard Webhooks specification.
- [ ] [Answer every webhook with a `2XX` status](https://signatureapi.com/docs/api/webhooks#retries): Any other status counts as a failed delivery. SignatureAPI retries for up to 48 hours with exponential backoff.
- [ ] [Handle events that arrive out of order](https://signatureapi.com/docs/api/webhooks#event-delivery): SignatureAPI does not guarantee the order of event delivery.
- [ ] [Retry `429` responses with backoff](https://signatureapi.com/docs/api/rate-limiting): Wait 1 second, then double the wait time after each `429` response.
- [ ] [Confirm ceremony outcomes on your server](https://signatureapi.com/docs/embedded/ceremony-events#confirm-the-outcome-on-your-server): A ceremony event is a UI signal, not proof. Read the envelope or use a webhook before acting on `ceremony.completed`.
- [ ] [Review your branding](https://signatureapi.com/docs/api/resources/envelopes/branding): Check the logo, colors and emails recipients will see.

## Set Up Live Senders

If your envelopes name a custom `sender`, register that address again with live mode on. Senders don't carry over from test mode, and only a `verified` sender can appear on an envelope. Verification needs the address owner to click a link that SignatureAPI emails them, so start early. See the [sender lifecycle](https://signatureapi.com/docs/api/resources/senders/lifecycle).

## Watch for Failures

A live envelope can fail after the API accepted it. Subscribe your live endpoint to the events that need someone's attention, and alert on them:

| Event                                                                                                                 | What happened                                                                                                                                                       |
| --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`envelope.failed`](https://signatureapi.com/docs/api/resources/events/envelope-events#envelopefailed)                | The envelope hit an internal error and moved to `failed`. `data.detail` explains why.                                                                               |
| [`recipient.hard_bounced`](https://signatureapi.com/docs/api/resources/events/recipient-events#recipienthard_bounced) | The signing request email to a recipient was rejected. Fix the address and [replace the recipient](https://signatureapi.com/docs/api/resources/recipients/replace). |
| [`recipient.rejected`](https://signatureapi.com/docs/api/resources/events/recipient-events#recipientrejected)         | A recipient declined to sign.                                                                                                                                       |
| [`deliverable.failed`](https://signatureapi.com/docs/api/resources/events/deliverable-events#deliverablefailed)       | The signed documents could not be generated.                                                                                                                        |

Also log every API error your code gives up on. [Retries and errors](https://signatureapi.com/docs/api/guides/how-to/retries-and-errors) explains which errors are worth retrying.

## Decide How Long to Keep Data

SignatureAPI keeps envelopes and their documents until you delete them. Decide where your signed documents live and when you delete envelopes before real personal data starts to flow. See [Data retention and deletion](https://signatureapi.com/docs/api/guides/best-practices/data-retention).

## Run a Last Live Test

Send one live envelope to yourself and sign it. Check that the email arrives from the right sender with your branding, that your live endpoint receives the events, and that the signed PDF reaches the place you store it. A live envelope counts toward your plan.
