Go to Production

We are getting closer to production. The excitement is real! Now that you have everything set in the development environment, there are few things you need to do:

Change Flinks Connect and API URLs

The first step to make sure you are ready to go to production is to change all Flinks Connect and API calls to your private instance.


Private instance

If you still don't have access to a private instance, send a message to our Growth Team at [email protected] and we will set you up!

Flinks Connect URL

In case you're using a sandbox instance, your iframe URL will look like this:


Assuming hypothetically that your private instance is called acme, your production Flinks Connect URL would be:



Similarly, your API path for the sandbox environment would look like this:


For the API calls the name of the production environment isn't the only part that changes, as the CustomerId does too.


Remember that your production CustomerId will also be different!

Still assuming that your API production instance is called acme and your production CustomerId is 6de65f1b-9c8e-421e-9add-ff989f31bc98, your new API path would be:


Let us know when you're going live!

When your integration is completed and you are ready to go live, one last step is required to successfully launch in production: an integration review by our Integration Team. To do so, please reach out to our team at [email protected].

Once approved, you are good to go. Three cheers! :rocket:


Let's review what you need to do before going to production:


Smooth Launch

  • Change the iframe URL to your production environment

  • Make sure all API calls are using the same production environment and the correct CustomerId

  • Get in touch with us for a review from our Integration team — we can't wait to hear from you!