Skip to main content
GET
Get a website article

Authorizations

Api-Token
string
header
required

Server-to-server authentication. Generate a token in the admin UI at Settings → Developers → API Access. Send the raw token in the Api-Token header — there is no Bearer prefix.

Tokens can be marked read-only at creation time, in which case the API rejects any non-GET request with 403 Forbidden.

Path Parameters

uuid
string
required

WebsiteArticle identifier

Response

WebsiteArticle resource

One article on a tenant's public website: news, an update, a story.

Every organisation this builder is meant to hold publishes these. All four reference sites carry a news index and article pages, and until now the builder had no answer: an admin could make a page per article, which is a page list nobody can maintain past a dozen, and a "latest news" row that would have to be rebuilt by hand every time.

This is deliberately not App\Entity\Post. That is the members' feed - written by anyone, moderated, reacted to, and scoped to what a member may see. An article is editorial: written by an admin, addressed to the public, and part of the site rather than of the community. Sharing a table would mean every query for one carried the other's rules.

The body is the same block list a page has, through the same sanitizer, so everything the catalogue can express is available in an article - and an agent that has learned the block vocabulary already knows how to write one.

uuid
string | null
slug
string
default:""
title
string
default:""
excerpt
string | null
coverImage
string | null
category
string | null
blocks
(string | null)[]
status
string
default:DRAFT
publishedAt
string<date-time> | null
seoTitle
string | null
seoDescription
string | null
dateCreated
string<date-time>
read-only
dateUpdated
string<date-time> | null
read-only