Retrieve a website page
One page of a creator website, with its document. Needs content: read.
This is how an agent that has lost its local copy reads a page back. html is exactly what was written, byte for byte: Commune stores it unchanged and injects search metadata when it serves the page rather than when it keeps it.
Request
- Base URL: https://api.usecommune.com
- URL: https://api.usecommune.com/website-pages/{page}
- Auth: one of:
- HTTP bearer
- OAuth 2 (authorization code, authorization URL https://usecommune.com/api/oauth/authorize, token URL https://usecommune.com/api/oauth/token, scopes: content:read)
Query parameters
Comma-separated list of relationship paths to inline in the response. Unexpanded relationships are returned as a reference object carrying only id and object. Each operation documents the paths it accepts, and an unknown path answers 400. Nested paths use a dot, for example article.newsletter.
Comma-separated allow-list of top level properties to return on each object, so a client can trim a response it does not need in full. id and object are always returned. An unknown property name answers 400. Properties omitted by an operation, such as content on any article list, cannot be brought back with fields.
Response
The page.
Example response
{
"newsletter": {
"object": "newsletter",
"id": "9a4c1c6e-0f2b-4f47-9d3f-6d1b1a2c3d4e"
},
"path": "/about"
}Changes
No recorded changes to this operation across all 1 revision of this API.