Publish a website page
Gives a page a public address. Needs content: write, and is a write.
Live immediately: there is no deploy step and no build. A newsletter page going live is also the moment Commune starts linking the newsletter's name and avatar at your website instead of at its page on Commune.
published_at is stamped the first time and never moved, so unpublishing and publishing again keeps the date the page first went up. Publishing a page that is already published succeeds and changes nothing.
Publishes no event.
Request
- Base URL: https://api.usecommune.com
- URL: https://api.usecommune.com/website-pages/{page}/publish
- 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:write)
Headers
A value of your choosing naming the change this request is making.
Send the same value again to retry the same request. Commune replays the answer the first attempt gave instead of making the change twice, and marks the replay with an Idempotent-Replay: true response header. Send a different value for a different change: a key reused for a request that differs in any way answers 409, because replaying an answer to a question you did not ask is a wrong answer you could not detect.
A UUID per change is the usual choice. Remembered for 24 hours, per credential, so two credentials choosing the same value never see each other's answers.
Required, not optional.
Response
The page, published, with the address it now answers at.
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.