Skip to main content

​
Read content in the consumer application

Your consumer application fetches the Content Document by the Landing Page’s Public ID (public_id). Reads are public: no account or token is required.

​
Fetch the Content Document

The 200 OK response is the Content Document itself, without the landing_page wrapper used by management routes:
Use the public_id returned when you create the Landing Page. The id is only for authenticated management routes and does not work here. Every read returns the current document: after an update, the next read already returns the new content.

​
Unknown identifier

An unknown public_id returns 404 Not Found:

​
Rate limits

Public reads are rate limited per IP each minute: When the limit is exceeded, the API returns 429 Too Many Requests with the Retry-After: 60 header:
For browser reads in production, register your frontend hosts in allowed_hosts.