Platform · Public document API

Fetch published legal text as JSON for apps and sites.

Your app needs the current Privacy Policy text programmatically. The public document API serves published content as structured JSON - no auth required for public docs.

What the public document API provides

JSON document payloads

GET /docs/[orgSlug]/[docSlug] returns document metadata and content for published versions - ready for rendering in your UI.

CORS enabled

Browser clients on your marketing site or web app can fetch public documents cross-origin without proxy hacks.

Version parameter

Request a specific published revision with the ?v=N query parameter when you need historical text.

Cache-friendly responses

Responses include a five-minute cache TTL - balancing freshness after publishes with efficient CDN and client caching.

Pairs with hosting

The API reads the same published versions served on Lawcel-hosted legal pages - one source of truth for human and programmatic consumers.

No API key for public docs

Published documents are public by design. Authenticated REST API endpoints remain separate for org-private operations.

Typical uses

One publish, many consumers

Legal publishes an approved version in Lawcel. Your marketing site links to the hosted page while your product app pulls JSON from the public API to show in-app terms acceptance.

When legal publishes an update, both the hosted page and API reflect the new version after cache expiry.

Publish in Lawcel

Legal team publishes the document version customers should see. Slug and org slug determine the API path.

Fetch from your app

Call the public endpoint from server or client code. Handle caching in your app layer if you need sub-five-minute freshness.

Stay in sync

Avoid hard-coding legal text in repos. Point at Lawcel so updates propagate without redeploying application code.

FAQ

No for published public documents. Unpublished or draft content is not exposed through this endpoint.
Responses cache for five minutes. Plan acceptance flows accordingly or fetch server-side with refresh logic for critical updates.
REST API v1 lists all org documents with auth for internal tooling. The public document API serves published content only, without a key.
Each request returns one published document by slug. Batch patterns typically loop known slugs from your app or CMS.
Yes. The endpoint serves published versions only. Document publishing is a Pro-plan capability - see pricing.

Ready to get started with Public document API?

Wire Lawcel into your stack - or start with a free scan of your public legal pages.

Try for free All integrations