Go-live checklist

Use this checklist to ensure a smooth transition when taking your integration live.

Openfort has designed its live and test modes to function as similarly as possible. Flipping the switch is mostly a matter of swapping your API keys.

1. Set the API version#

To make sure everything is in sync:

  • For dynamic languages (Node.js): set the API version in the server-side library
  • For strongly typed languages (TypeScript, .NET): upgrade to the latest version of your chosen library

2. Review your API error handling#

Once you’ve gone live is an unfortunate time to discover you’ve not properly written your code to handle every possible error type, including those that should “never” happen. Be certain your code is defensive, handling not just the common errors, but all possibilities.

3. Review your logging#

Openfort logs every request made with your API keys, with these records being viewable in the Dashboard(coming soon). We recommend that you log all important data on your end, too, despite the apparent redundancy. Your own logs will be a life-saver if your server has a problem contacting Stripe or there’s an issue with your API keys—both cases would prevent us from logging your request.

4. Ensure you've registered your production webhooks#

Your Openfort account can have both test and live webhook endpoints. If you’re using webhooks, make sure you’ve defined live endpoints in your Openfort account. Then confirm that the live endpoint functions exactly the same as your test endpoint.

While examining your webhooks status, also take a moment to check that your production endpoint:

  • Gracefully handles delayed webhook notifications
  • Gracefully handles duplicate webhook notifications
  • Does not require event notifications to occur in a specific order