Skip to content

Legal pages API

Read terms, privacy, refund, cookie and other policies with their current version, effective date, change history and earlier versions.

Legal pages (terms, privacy, refund, cookie, acceptable use, AI usage) keep versions. Apps read them from the content API and show them under their legal path.

List

curl https://blogs.remplatforms.com/api/public/self/pages -H "Authorization: Bearer $REM_CONTENT_TOKEN"
curl "https://blogs.remplatforms.com/api/public/self/pages?kind=terms" -H "Authorization: Bearer $REM_CONTENT_TOKEN"

Each item: title, path, kind, footer label and column, version, effective date and its URL on the app's domain. Use it for footers and a legal index.

One page

curl https://blogs.remplatforms.com/api/public/self/pages/terms -H "Authorization: Bearer $REM_CONTENT_TOKEN"

The answer has title, summary, content_html, toc, blocks, updated_at, is_legal, the current version and effective_from, seo, and history: the last 50 versions with version, effective_from, published_at, change_note and material.

An earlier version

curl https://blogs.remplatforms.com/api/public/self/pages/terms/versions/2 -H "Authorization: Bearer $REM_CONTENT_TOKEN"

Returns that version's text with current_version, its own url (.../terms?version=2) and canonical_url (the current page). Show it when someone asks which terms applied on a date.

Download

GET /{product}/pages/{path}/download?format=pdf (also docx, odt, html, md).

With the SDK

import { LegalPage, LegalIndex } from '@rem/content-react';

const page = await content.page('terms');
return <LegalPage page={page} />;        // body, effective date, change history

A material version with users must accept set is your app's cue to ask signed-in people to accept the new version at their next visit.

Last updated 18 Nov 2026

Legal pages API · REM Blogs