Configuring Entri requires just a few simple steps:

1. Set up your account

The first step to getting up and running with Entri is to configure your application display name and icon in the dashboard. These will be used in the Entri modal.

For the icon, we require a PNG or SVG with a 1:1 ratio. We recommend a white or transparent background.

From the dashboard, you can also access your application ID, webhook URL, and client secret, which you’ll need for the next steps.

2. Add the Entri <script> tag

<script type="text/javascript" src=""></script>

Add this tag to your HTML. This creates a global entri variable on the page, so make sure the Entri tag is placed above any JavaScript that references it.

3. Fetch the JSON web token (JWT)

To launch the Entri modal window in a session, you’ll need to fetch a JWT using the secret key and applicationId provided by the Entri dashboard. Be sure to fetch the JWT on the server-side of your application. The JWT expires after 60 minutes. You can use any networking library you’d like. Here’s an example usingfetch:

fetch('', {
  method: 'POST',
  body: JSON.stringify({
    // These values come from the Entri dashboard
    applicationId: "12345",
    secret: "12345-67890"
.then(response => response.json())
.then(data => {
  console.log('Success:', data); // { "auth_token": "exampletoken..." }
  // Save the token in a variable or state manager for later use
.catch((error) => {
  console.error('Error:', error);

4. Create the configuration object

Pass settings to the Entri modal window using a configuration object. Here’s a basic example:

const config = {
  applicationId: "12345", // From the Entri dashboard
  token: mySavedToken, // The "auth_token" value saved in the previous step
  dnsRecords: [
      type: "CNAME",
      host: "www",
      value: "",
      ttl: 300,
      type: "TXT",
      host: "@",
      value: "sample-txt-record",
      ttl: 300,
      type: "MX",
      host: "host",
      value: "",
      priority: 10,
      ttl: 300,

Configuration Object Notes

  • MX records require a priority

For complete documentation of the configuration object, see the API Reference.