Sites

Zero-based index of this page.

How many rows a full page holds.

The rows on this page, in the order that was asked for.

How many sites match, across every page — which is what the pager is against. Equal to TotalOwned when no search was asked for.

How many sites the caller owns, ignoring any search.

Both numbers, because the listing says both: the page header counts what the account holds and the line above a searched list counts what matched. One number cannot carry that sentence, and a client holding the other from an earlier response has a number that a deletion can make wrong.

Plaintext claim token, present only for an anonymous site and returned only here. The server keeps nothing but its hash, so a client that loses it cannot recover ownership.

When an unclaimed anonymous site is removed. Null once the site has an owner.

ULID of the new site.

Allocated subdomain, without the parent domain.

Public HTTPS URL the site will answer on once a deploy goes live.

Sites now owned by the caller.

Sites that were not claimed, each with a reason. A batch can be partly successful, so this is not an error case — the caller shows what it got and drops the rest from local storage.

Whether this name could be used right now.

The name as it would actually be stored, lowercase and trimmed. Null when the input failed format outright, in which case there was nothing to normalize.

Why not, using the same codes POST /sites would answer with. Null when Available is true.

How many days of traffic this site's plan allows seeing, or zero when it includes none. Sent for the same reason as the flag above: the page can state what the plan covers instead of requesting the figures and rendering a refusal.

Whether this site's plan is sold with the traffic export. Read from the site's own plan rather than from the signed-in account's, because the two differ — an anonymous site is on the anonymous tier whoever is looking at it.

Whether the site has no account behind it.

Stated rather than inferred, and it replaces an inference the dashboard was making from ExpiresAt being set. That proxy held only while an expiry meant one thing: now that an owner can schedule a takedown on a site of their own, a paid site with a date on it would have read as anonymous and been told it gets deleted after a few days.

Whether this site's plan lets its owner edit a file in the browser. Sent so the file list can leave the Edit action out rather than offering one the server refuses.

Who the owner chose may comment — Off, Invited or Anyone. The stored choice; it takes effect only where FeedbackAvailable is true and, for Invited, while the site is invite-only, which the Sharing tab says in words.

When the site was created.

How many hostnames of the customer's own this site's plan allows across the account, or zero when it includes none.

Sent here rather than looked up from the public plans list, which is where the dashboard read it and where it is not always findable: GET /plans filters to public tiers, so a site on a plan cut for one account matched nothing and the section rendered as a heading with nothing underneath — exactly the account most likely to have been given an allowance. The same argument as PasswordProtectionAvailable, which is why it sits beside it.

The most recent deploys, newest first.

Whether the site is served through the documents viewer.

When an unclaimed anonymous site is removed, or null once claimed.

What the expiry does when it falls due, Pause or Delete. Meaningless while ExpiresAt is null, and sent anyway so the form has something to show when the owner sets a date.

Whether this site's plan includes comments. Sent for PasswordProtectionAvailable's reason: the control shows disabled with a reason rather than failing on submit.

The folder it is filed in, or null when it sits at the root of the listing.

The same field SiteSummary carries. Sent here as well so the site's own page can put that folder in its trail and return to it — after a removal, too — instead of to the root of the listing, which is where somebody who opened the site from inside a folder did not come from.

The names the site used to answer on, newest first, each redirecting to it.

Whether the account's tier includes forms at all.

Reported beside the switch for the reason PasswordProtectionAvailable is: the dashboard has to tell "off" apart from "not yours to turn on", and a control that looks available and then refuses is worse than one that says why.

Whether the owner has switched form submissions on for this site.

Whether only the people on the site's list may see it. Never true together with PasswordProtected.

Whether this site's plan offers invite-only sites. Sent for PasswordProtectionAvailable's reason: the Sharing tab shows the third choice disabled with a reason rather than offering it and failing.

When it last received a deploy.

The deploy being served, or null.

How many people this site's plan lets the list hold, the owner included — and, per site, how many invitations it may mail in a day.

Whether the serving mode was chosen by the owner rather than detected from the files of the deploy that went live. What lets the dashboard say which of the two it is showing.

What to call it, or null when it has none and the subdomain should be shown instead.

A label only. The site is reached by Subdomain whatever this says, which is why the dashboard shows the address underneath rather than replacing it: two sites are allowed the same name, and the name is not what anybody types into a browser.

Threads open on the site, the number on the Feedback tab.

Whether visitors must enter a password. Only whether one is set is reported — the password itself is stored as a hash, so there is nothing to return.

Whether this site's plan permits a password at all. Sent so the dashboard can show the control in a disabled state with a reason, rather than offering it and failing on submit.

Plan whose limits apply.

The URL to lead with: a hostname of the customer's own once one is serving, and Url otherwise.

Sent as its own field rather than by overwriting Url, because the two are not interchangeable and the subdomain does not stop mattering: it needs no DNS of anybody's and keeps working when a custom domain's records are changed or lapse, which makes it the address to fall back to when the other one is what is being diagnosed.

Whether readers of this documents site see each document's views and downloads. Every plan may turn it on.

Whether this site's plan lets its owner schedule when it comes down. Sent so the dashboard can show the control disabled with a reason rather than offering it and failing on submit.

ULID of the site.

Whether an unmatched path falls back to index.html.

Whether the site is serving, and if not, who switched it off — the SiteStatus name.

What the pause control reads, and what tells the three off-states apart for the customer. They need different words and different offers: their own pause has a button that undoes it, a suspension has support to contact, and being held for quota has an upgrade. One boolean could not say which.

When the state last changed, or null if it never has.

Its subdomain.

How many more times the owner may change Subdomain, or null when the plan does not limit it. What the change-of-address control and its confirmation show.

Whether this site's plan includes top lists, the globe and filters on the traffic page. Sent so the page draws a locked card naming the tier instead of requesting a list and rendering a 403.

Whether this site's plan splits people from bots and AI and shows devices, browsers and campaigns.

Its public URL on the platform's own content domain.

ULID of the deleted site.

Its subdomain, which stays reserved.

Who the owner chose may comment — Off, Invited or Anyone. The stored choice, which takes effect only where the plan and the viewing mode allow it.

The setting as it now stands.

When the site is now scheduled to come down, or null when it has no schedule. Echoed because the request sends a string and this is the instant it parsed to.

What that schedule will do. Reported even when ExpiresAt is null, where it is the choice a future date would inherit.

The folder the site is now filed in, or null when it sits at the root. Echoed so a client that sent "root" reads back the null it produced rather than the token it sent.

Whether this site accepts form submissions. The site's own switch, which the tier has to permit before the edge honours it — so a site on a tier without forms reports false here and cannot be set to true.

Whether only the people on the site's list may now see it. Never true together with PasswordProtected.

Whether the hostname mapping was rewritten. False for a site that has never published, where the setting is stored and takes effect with its first deploy.

Whether the serving mode shown here was chosen by the owner rather than detected from the files.

Reported so the dashboard can say which it is. A control that renders a detected value identically to a chosen one tells the owner they picked something they never picked, and hides the one fact that explains why the mode changed after a deploy — or why it stopped changing.

The name as it now stands, or null when the site has none and the dashboard should show its subdomain. Echoed back because cleaning can change what was sent.

Whether the site now requires a password. The password itself is never returned — only the hash is stored, so there is nothing to return even if it were wanted.

Whether readers see each document's views and downloads.

ULID of the site.

The setting as it now stands.

The site's custom domains, oldest first, excluding ones that were given up. Empty for a site with none, which is every site until somebody adds one.

The bare domain this www hostname sits directly on, or null when it is not a www hostname or sits on something else.

What the dashboard needs to offer "send example.com here too": a bare domain cannot point at this platform, so the customer redirects it to the www name at their DNS provider. Read from the zone the nameserver lookup found when the domain was added, which is what makes www.example.com.vn answer example.com.vn; a row added before that was recorded falls back to the two-label case.

Whether the certificate has been issued, which is what says the DCV records are done rather than missing.

Sent because the provider stops returning those records the moment the certificate exists, including when it validated over HTTP without the customer adding anything. Without this the dashboard reads an empty list as "not issued yet" and the rows vanish from under somebody who is still copying them.

What the customer points their hostname at, once both validations pass. Served rather than hardcoded in the frontend for the reason every other piece of configuration is: a customer told the wrong target gets a hostname that validates and then never serves.

When the customer asked for the hostname.

Name of the certificate validation TXT records, or null once none is needed.

Values of the certificate validation TXT records, or empty once none is needed.

Several under one name: the certificate is issued as a pack and each member is validated separately, so the customer has more than one record to add and adding one of them satisfies nothing.

Who serves DNS for the hostname, as the lowercase name of DnsProvider, and therefore which order the dashboard has to ask for the records in.

The hostname, normalized.

ULID of the domain row, used to remove or re-check it.

Name of the ownership TXT record, or null once it is no longer needed.

Value of the ownership TXT record, or null for the same reason.

Whether the customer asked for the no-gap path and could not have it, because the certificate provider will not pre-validate a hostname whose zone it is already authoritative for — which is what DnsProvider reports when the customer's own DNS sits with the same provider.

Sent so the dashboard can say so. The override is right — the path they asked for cannot complete and the one they got does — but a customer who ticked the box to protect a live site and is told nothing will point their DNS here believing there is no gap, and learn otherwise from their own visitors.

Where it is between being asked for and serving, as the lowercase name of SiteDomainStatus.

How the certificate is being proven, as the lowercase name of CertificateValidation, and therefore how many records to show.

"http" is one CNAME and nothing else. "txt" is the no-gap path a customer asked for because their hostname is already serving, and carries the record pairs above. Sent rather than inferred from those pairs being empty, which is what an "http" row and a finished "txt" row would otherwise look like alike.

Why the certificate provider has not activated the hostname, in its words, or empty when it has nothing to say.

When both validations first passed, or null while still pending.

The hostname that stopped serving.

ULID of the domain that was removed.

The bare domain this www hostname sits directly on, or null when it is not a www hostname or sits on something else.

What the dashboard needs to offer "send example.com here too": a bare domain cannot point at this platform, so the customer redirects it to the www name at their DNS provider. Read from the zone the nameserver lookup found when the domain was added, which is what makes www.example.com.vn answer example.com.vn; a row added before that was recorded falls back to the two-label case.

Whether the certificate has been issued, which is what says the DCV records are done rather than missing.

Sent because the provider stops returning those records the moment the certificate exists, including when it validated over HTTP without the customer adding anything. Without this the dashboard reads an empty list as "not issued yet" and the rows vanish from under somebody who is still copying them.

What the customer points their hostname at, once both validations pass. Served rather than hardcoded in the frontend for the reason every other piece of configuration is: a customer told the wrong target gets a hostname that validates and then never serves.

When the customer asked for the hostname.

Name of the certificate validation TXT records, or null once none is needed.

Values of the certificate validation TXT records, or empty once none is needed.

Several under one name: the certificate is issued as a pack and each member is validated separately, so the customer has more than one record to add and adding one of them satisfies nothing.

Who serves DNS for the hostname, as the lowercase name of DnsProvider, and therefore which order the dashboard has to ask for the records in.

The hostname, normalized.

ULID of the domain row, used to remove or re-check it.

Name of the ownership TXT record, or null once it is no longer needed.

Value of the ownership TXT record, or null for the same reason.

Whether the customer asked for the no-gap path and could not have it, because the certificate provider will not pre-validate a hostname whose zone it is already authoritative for — which is what DnsProvider reports when the customer's own DNS sits with the same provider.

Sent so the dashboard can say so. The override is right — the path they asked for cannot complete and the one they got does — but a customer who ticked the box to protect a live site and is told nothing will point their DNS here believing there is no gap, and learn otherwise from their own visitors.

Where it is between being asked for and serving, as the lowercase name of SiteDomainStatus.

How the certificate is being proven, as the lowercase name of CertificateValidation, and therefore how many records to show.

"http" is one CNAME and nothing else. "txt" is the no-gap path a customer asked for because their hostname is already serving, and carries the record pairs above. Sent rather than inferred from those pairs being empty, which is what an "http" row and a finished "txt" row would otherwise look like alike.

Why the certificate provider has not activated the hostname, in its words, or empty when it has nothing to say.

When both validations first passed, or null while still pending.

Whether the site may run functions now. False, the variables are kept but none reaches the edge, and none can be set.

Largest total of a site's values, in UTF-8 bytes.

Largest value of one variable, in UTF-8 bytes.

Most variables a site may hold.

The values' total size, in UTF-8 bytes.

The variables, by name.

When it was first set.

The value's last four characters, or empty for a short value.

The name.

When its value last changed.

Whether the site's plan includes comments.

Comments the site holds, deleted ones not counted — what the plan's ceiling counts.

The plan's ceiling on comments per site.

Threads open on the site.

The page returned, from 0.

Rows per page.

Every page that has a thread, for the page filter.

Threads resolved on the site.

The comments, newest first.

Comments matching the filter.

The page returned, from 0.

Rows per page.

Most recent first.

Everybody blocked on the site.

How many of their comments were deleted now.

The person, as the Blocked list names them.

The largest change value on the site at the moment of the read; send it as since to get only the threads that changed after.

Whether another page follows.

The page returned, from 0.

The threads, in the order they were opened.

Its comments, oldest first; deleted ones left out.

When it was opened.

Thread id, for replying and resolving.

Whether it was opened on an earlier version than the one the site serves now — the words it points at may have changed since.

The page it is on: a path on the site, or a document's path in a documents site.

Where on the page.

When it was resolved, or null while open.

Who resolved it, by name, or null while open.

The link that opens the page at the thread.

Its comments, oldest first; deleted ones left out.

When it was opened.

Thread id, for replying and resolving.

Whether it was opened on an earlier version than the one the site serves now — the words it points at may have changed since.

The page it is on: a path on the site, or a document's path in a documents site.

Where on the page.

When it was resolved, or null while open.

Who resolved it, by name, or null while open.

The link that opens the page at the thread.

Its comments, oldest first; deleted ones left out.

When it was opened.

Thread id, for replying and resolving.

Whether it was opened on an earlier version than the one the site serves now — the words it points at may have changed since.

The page it is on: a path on the site, or a document's path in a documents site.

Where on the page.

When it was resolved, or null while open.

Who resolved it, by name, or null while open.

The link that opens the page at the thread.

Whether this site's switch is on, so the tab can say why nothing is arriving.

One row per form name, most recently used first.

What the account's tier allows a month. Zero means forms are not part of it.

Submissions the account has taken this calendar month, across every site it owns. The figure the allowance is measured against, which is why it is not the site's own count.

Zero-based index of the page returned.

How many rows a page holds, after the cap was applied.

The page, newest first.

How many this form has in total, so the reader knows there is more.

Whether the owner has it switched off, whatever the status says.

ULID of the site.

Its lifecycle state, one of SiteStatus as text.

When the state last changed, or null if it never has.

The subdomain it is addressed by, whether or not it is serving.

Whether the owner has it switched off, whatever the status says.

ULID of the site.

Its lifecycle state, one of SiteStatus as text.

When the state last changed, or null if it never has.

The subdomain it is addressed by, whether or not it is serving.

The names it used to answer on, newest first, each redirecting here.

ULID of the site.

The subdomain it answers on now.

How many more changes its plan allows, or null when it allows any number.

Its URL on the content domain.

When the Analytics Engine figures were read, or null when none were.

False when Analytics Engine could not be read and nothing was kept.

Days the lists, globe and status split cover — the range, capped at what Analytics Engine keeps.

Width of a chart point: hour, day or week.

Its length in days.

The documents table, by UTC day.

First instant of the range, UTC.

First day anything was rolled up for this site, or null.

The range as the page spells it: 24h, 12m, or {N}d.

Whether any figure is an estimate from sampled rows.

The chart, or null when Analytics Engine could not be read.

Where the chart and tiles start: From, except on a filtered range longer than BreakdownDays, where only the breakdown window can be filtered.

False when the speed figures were asked for and could not be read, so a null Speed means "couldn't load" rather than "nothing measured".

First whole day bots were counted apart from people and arrivals were recorded, or null when not yet. Before it, people include bots and visits are unknown; the page marks the day. Equal to MeasuredSince for a site that was split from its first day, which has no "before".

End of the range, exclusive: the top of the next hour.

When it was read from Analytics Engine, or null.

False when the list could not be read and nothing was kept.

Days the list covers.

Which list: page, referrer, country or notfound.

First instant the list covers — the breakdown window, not always the range.

Values, busiest first, or null when the list could not be read.

The range asked for.

Whether any count is an estimate from sampled rows.

End of the window, exclusive.

The account's proxied requests this month against its plan.

Most upstreams a site may declare.

Whether the platform switched this site's proxy off (D17): every proxy route answers 404 until it is lifted, whatever the upstreams say.

The proxy routes the live version's _redirects declares; empty when it has none.

The site's upstreams, oldest first.

Whether the platform blocked this origin for every site (D17): calls to it answer 502 until the block is lifted.

When it was declared.

Header names and the last four characters of each value.

Upstream id.

Methods visitors may send, GET implying HEAD.

https://host.

When it last changed.

When the entries were read, or null when they were not.

False when the log could not be read: no dataset configured, or Analytics Engine down.

Latest proxied requests, newest first.

Whether the platform blocked this origin for every site (D17): calls to it answer 502 until the block is lifted.

When it was declared.

Header names and the last four characters of each value.

Upstream id.

Methods visitors may send, GET implying HEAD.

https://host.

When it last changed.

Whether the plan offers invite-only sites at all. A list can outlive the plan that allowed it, and is still shown so it can be shortened; adding to it is refused.

How many people are in each status, ignoring the search and filter.

Whether the site is currently open only to the people listed.

The most people this site's plan allows on the list, the owner included.

The zero-based page returned.

Rows per page.

How many rows match the search and filter, across every page.

The rows on this page: the owner's first, then the most recently added.

The addresses newly put on the list, as stored.

The addresses sent that were on the list already, left as they were.

How many people the list now holds, the owner included.

The address removed, as it was stored.

How many people the list still holds, the owner included.