Power Endpoints

​

Power API - Custom domains

​

List powered domains

GET https://api.goentri.com/power
Header "Authorization: [JWT authorization]"
Header "applicationId: [yourApplicationID]"

​

Headers

​

Query string parameters

Note: status is optional. If omitted, the endpoint returns all powered domains for the application.

​

Sample response

{
  "items": [
    {
      "domain": "www.example.com",
      "applicationUrl": "my.applicationurl.com",
      "powerRootPathAccess": ["/", "/shop"],
      "powerStatus": "active"
    },
    {
      "domain": "blog.example.com",
      "applicationUrl": "my.applicationurl.com",
      "powerRootPathAccess": [],
      "powerStatus": "inactive"
    }
  ],
  "total": 2,
  "page": 0,
  "limit": 50,
  "count": 2,
  "pages": 1,
  "nextPage": null,
  "prevPage": null
}

​

Field definitions

• domain (string): Fully qualified domain or subdomain configured via Power.
• applicationUrl (string): Current upstream URL for this domain.
• powerRootPathAccess (string[]): List of root paths with access granted (may be empty).
• powerStatus (string): active or inactive.
• total (integer): Total number of powered domains matching the filter.
• page (integer): Current zero-based page index.
• limit (integer): Maximum number of items requested per page.
• count (integer): Number of items returned.
• pages (integer): Total number of pages available.
• nextPage (integer | null): Next page index, or null if not applicable.
• prevPage (integer | null): Previous page index, or null if not applicable.

​

Error responses

​

Rate limits

​

Example cURL

curl -X GET "https://api.goentri.com/power?status=active&size=10&page=0 \
  -H "Authorization: Bearer <JWT>" \
  -H "applicationId: <yourApplicationID>"

​

Check the domain’s eligibility

GET https://api.goentri.com/power?domain=www.example.com&rootDomain=false
Header "Authorization: [JWT authorization]"
Header "applicationId: [yourApplicationID]"

​

Parameters description

​

Successful response (200 status)

{
  // Is the domain CNAMEed to the cname_target of the application?
  "eligible": true | false,

  // Is the domain already powered?
  "powerStatus": "active" | "inactive",

  // Current cnameTarget set on the Dashboard
  "cnameTarget": URL | "",

  // Current cnameTarget value for the domain
  "applicationUrl": URL | "",

  //Paths with granted access to the root of the Application URL
  "powerRootPathAccess": [] | ["/path1", "/path2",..., "pathN"]
}

​

Possible error responses

​

Power a new domain

POST https://api.goentri.com/power
Header "Authorization: [JWT authorization]"
Header "applicationId: [yourApplicationID]"

​

Request body

{
  "domain": "www.example.com",
  "applicationUrl": "my.applicationurl.com"
}

​

Successful response (200 status)

{ "message": "Success." }

​

Possible error responses

​

Update an already powered domain

PUT https://api.goentri.com/power
Header "Authorization: [JWT authorization]"
Header "applicationId: [yourApplicationID]"

​

Request body

{
  "domain": "www.example.com",
  "applicationUrl": "my.applicationurl.com"
}

​

Successful response (200 status)

{ "message": "Success." }

​

Possible error responses

​

Remove a powered domain

DELETE https://api.goentri.com/power
Header "Authorization: [JWT authorization]"
Header "applicationId: [yourApplicationID]"

​

Request body

{ "domain": "www.example.com" }

​

Successful response (200 status)

{ "message": "Success." }

​

Possible error responses

​

Appended Headers on Incoming Traffic

• X-Forwarded-Host: This header contains the original 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-entri-forwarded-host: Similar to 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.
• X-Forwarded-IP or X-Forwarded-For: These headers contain the original IP address of the client making the request. It is useful for understanding where the request originated from, even if it passed through proxies or load balancers.
• X-Entri-Auth: The X-Entri-Auth header is a configurable authentication token that you can set in the Entri Dashboard. Once enabled, it is automatically included in every outgoing request, allowing your system to verify that the request originated from Entri. The token can be rotated at any time to align with your internal security policies.