Across 6 paths, the API surfaces 9 operations — 1 DELETE, 5 GET, 2 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
content 9
GET
/v1/org/{orgId}/content
Return all content in the organization paginated
findContent5 params→ 200400401404
POST
/v1/org/{orgId}/content
Create a new piece of content
createContent2 params→ 201400401403404
PATCH
/v1/org/{orgId}/content/homepage
Update the homepage content
updateHomepage2 params→ 204
GET
/v1/org/{orgId}/content/homepage/render
Render the contents of the homepage
renderHomepage1 param→ 200
GET
/v1/org/{orgId}/content/path/{path}
Return a particular content by path
getContentByPath2 params→ 200400404
GET
/v1/org/{orgId}/content/path/{path}/render
Return a particular content by path, and render its contents
renderContentByPath2 params→ 200400404
GET
/v1/org/{orgId}/content/{contentId}
Return a particular content by id
getContent2 params→ 200400404
PATCH
/v1/org/{orgId}/content/{contentId}
Update an existing piece of content
updateContent3 params→ 204400401403404
DELETE
/v1/org/{orgId}/content/{contentId}
Delete a content
deleteContent3 params→ 204400401403404
Schemas 12
The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Content (26 properties), UpdateContent (12 properties), CreateContent (11 properties), Attribution (6 properties). Each schema is shown below with its type and property counts.
AccessAction
object
3 properties1 required
ResultsContent
object
3 properties1 required
UpdateContent
object
12 properties
ResultsAccess
object
2 properties1 required
CreateContent
object
11 properties1 required
HomepageContentRender
object
1 property1 required
Translations
object
1 property1 required
Attribution
object
6 properties
ShareAccess
object
4 properties1 required
ContentRender
object
2 properties2 required
ContentBlock
object
2 properties1 required
Content
object
26 properties4 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
