Change a site's settings

You need the site write permission (the Owner and Admin roles) to save, and permission to deploy (Owner and Admin) for the change to reach requests.

Edit and save

1. Open Delivery › Delivery › Sites and select the site. Search by name or domain if the list is long.
2. In Settings, change any of Name, Domain, Status, Allowed and Redirect. Each field is described in Site settings.
3. Select Save. One save covers the whole section.

The change is now in the draft. Requests still use the values in your newest deployment.

Deploy

Deploy from Delivery › Deployments › Versions, as described in Stage and deploy a change. From that deployment on, every request to the site uses the new values.

Check the site resolves

After the deploy, ask for the site’s public sign-in descriptor. It needs no credential, so it is a quick way to see whether the site resolves:

curl -i https://your-tenant-host/v1/id/config \
  -H 'x-edgekit-site-id: site_daily_example'

const response = await fetch('https://your-tenant-host/v1/id/config', {
  headers: { 'x-edgekit-site-id': 'site_daily_example' },
});

console.log(response.status); // 200 when the site is active and deployed

200 means the site resolves. 404 not_found with Unknown site. means the id is wrong, the site is disabled, or the deploy that adds it has not happened. A 200 can be cached for up to five minutes, so disabling a site can take that long to show here.

Allow your site’s browser origins

A site with an empty Allowed list refuses with 403 every browser request that needs an allowed origin. Before your pages call EdgeKit from the browser, list every origin they run on in Allowed, one per line:

https://daily.example
https://www.daily.example

Write each origin exactly as the browser sends it in the Origin header: scheme, host in lower case, and port only if it is not the default. Leave out any path and the trailing slash: https://daily.example/ is refused when you save. Wildcards do not work: https://*.daily.example is saved but never matches. http:// origins are accepted, for example a local development server.

Disable a site

Set Status to disabled, save and deploy. The client API and decide then answer every request for the site with 404 not_found, the same answer as for a site that does not exist. Its API keys and its settings are kept, so setting the status back to active and deploying restores it. The console cannot archive or delete a site.

If the save is refused

Message	What to do
Domain is a hostname — no scheme, port or path.	Enter daily.example, not https://daily.example/.
Another site already uses that domain.	Each domain belongs to one site.
Allowed origins: "…" must be exactly …, with no path or trailing slash.	Use the origin the message shows.
Allowed origins accepts at most 50 entries.	Remove entries; the same limit applies to redirect origins.
Someone else changed this site while you were editing it. Reload and reapply your change.	Reload the page and make your change again.