With Entri Power, you can enable support for custom domains in just minutes.
cname_target
.
The cname_target
is the CNAME record that your end-users will eventually need to add. For example: domains.saascompany.com
After inputting the cname_target
on the Entri dashboard, you’ll need to create a CNAME record that points your cname_target
to power.goentri.com
on your domain’s DNS.
For example, if you run saascompany.com
and your cname_target
is domains.saascompany.com
, then you would add this record to the DNS for saascompany.com
:
power
and set it to true
.applicationUrl
. The applicationUrl
is the URL of your application that you would like to render on the customer’s domain. This will likely change for every user. For example, the applicationUrl
for a calendar booking app might look something like this: https://calenderapp.com/meetings/user-name
dnsRecords
array, and the value
as the {ENTRI_SERVERS}
placeholder. Make sure to also add your target application destination as the applicationUrl
key value. Entri will take care of the rest.
If you are prompting users to enter a domain in the Entri modal, make sure that you use dynamic configuration variables.
Sample configuration:
dnsRecords
array. Be sure that the value
is set to {CNAME_TARGET}
. If you are prompting users to enter a domain in the Entri modal, make sure that you use dynamic configuration variables.
Sample configuration:
GET
request to our API which confirms that the domain you want to power contains a CNAME record pointing to your cname_target
.
Use the following information for the GET
Request:
<https://api.goentri.com/power
>Authorization
header: The authorization JWT. You can Fetch your JWT using your Client Secret set in the configure section of the Entri Dashboard.applicationId
header: Your applicationId
can be found in the configure section of the Entri Dashboard.domain
in the GET
request body. domain
can be a root domain or a subdomain such as **www.**domain.com or site.domain.com.curl
:cname_target
, then our API will return "eligible": true
. If it does not contain cname_target
, then our API will return "eligible": false
. If it does not contain cname_target
and/or it already is an Entri-powered domain, then our API will return “eligible”: false
The rootDomain=true
parameter is used for whenever you are trying get the root domain’s Power status (not the subdomain).
GET
request returned "eligible": true
then you can proceed to the next step below.
POST
request in Step 2
(below) unless the domain returned "eligible": true
in theGET
request from
Step 1. Otherwise, the POST
request will be denied.cname_target
and therefore is eligible for Power, you can proceed with enabling the domain via a POST
request to our endpoint as detailed below:
<https://api.goentri.com/power
>Authorization
header: The authorization JWT. You can Fetch your JWT using your Client Secret set in the configure section of the Entri Dashboard.applicationId
header: Your applicationId
can be found in the configure section of the Entri Dashboard.domain
and the applicationUrl
in the POST
body. domain
must contain a subdomain such as **www.**domain.com or site.domain.comcurl
:
powerRootPathAccess
key in the Entri Power configuration. Below, you’ll find a sample configuration for each use case, modal, and API setup:
Host
value of the incoming request before any proxy or load balancer has modified it. It helps in identifying the initial destination for the request.
X-Forwarded-Host
, this is a custom header used by Entri to track the original host at the time the request was forwarded through Entri’s system.
applicationUrl
, make a PUT
request to our API using the following information:
<https://api.goentri.com/power
>Authorization
header: The authorization JWT. You can Fetch your JWT using your Client Secret set in the configure section of the Entri Dashboard.applicationId
header: Your applicationId
can be found in the configure section of the Entri Dashboard.domain
, the new applicationUrl
, and optionally the in the new powerRootPathAccess
whitelisted paths on the PUT
request body. domain
must contain a subdomain such as **www.**domain.com or site.domain.comcurl
DELETE
request to our API using the following information:
<https://api.goentri.com/power
>Authorization
header: The authorization JWT. You can Fetch your JWT using your Client Secret set in the configure section of the Entri Dashboard.applicationId
header: Your applicationId
can be found in the configure section of the Entri Dashboard.domain
in the DELETE
request body. domain
must contain a subdomain such as **www.**domain.com or site.domain.comcurl
applicationUrl