API
Read published Capell pages from a separate frontend.
- Version
- 1.1.0
- Released
- 10 November 2026
- Requires
- Layout Builder
- Licence
- Free
Price Free
Check access and installationCheck your application before checkout
What it solves
The problem
Our headless frontend cannot retrieve published pages without a custom integration.
What your site gets
A separate frontend can consume published page content without receiving draft or authoring state.
Questions buyers ask
- What content can a headless client retrieve?
- Resolve and list published pages, filter collections by page type, search titles and retrieve a paginated page directory and public content images through the supported v1 API.
- Are draft pages included in responses?
- Public reads exclude drafts. Server-side Sanctum tokens with explicit preview and site abilities can request sanitised preview content.
- Can clients use it to edit pages?
- The declared endpoints are public and read-only.
Use it in your project
Use the versioned API when another application needs page content and layout data. Responses contain published content suitable for public delivery.
Picture it on your site
For a separate frontend, choose one published page as the first integration and agree the data your client needs. Check the response shape, missing-page handling and layout presentation before extending it. Capell supplies the published content boundary; your team still builds and maintains the client application that turns it into an experience.
2 captures
Connect content to your website
- Resolve published pages through JSON endpoints.
- Request bounded layout data without private editing state.
Is this right for your project?
Choose the delivery boundary
Decide whether your application needs rendered pages, a separate frontend or another service reading published content. A delivery package is useful when it makes that boundary explicit instead of asking another system to understand private editing state. Your Laravel application still owns its routes, presentation and access decisions; the published contract is what a consuming frontend should build against.
Check a real consuming application
Test one published page from end to end, including its layout, language, missing-content response and links to other pages. Compare that with an unpublished page so you can see the boundary working. Plan how the consuming application refreshes content after a change, rather than assuming that an endpoint or successful response also solves caching and deployment.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Add this free package to your account, then review compatibility and site impact before installing it.
This listing has no page of its own in the demo. Open the demo to see Capell running.
Before you install
Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.
- Admin and public surfaces
- The package declares: frontend integration, public routes. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- The manifest declares no package migrations. This does not establish that installation or runtime operations make no data changes. May connect configured Capell content, media, or integration metadata to the named service boundaries for this package.
- Background work
- A complete jobs and scheduler assessment is not available here. Confirm background processing and worker requirements with the publisher.
- Access controls
- Access-control changes are not described here. Confirm the required roles and grants with the publisher.
- Removal and retained data
- A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
-
01
Require the package
composer require capell-app/api -
02
Install the extension
php artisan capell:extension-install capell-app/api
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.0 Nov 10, 2026
- Recent activity
- 14 approved releases in the last 12 months
Review evidence for this release
Read-only content API reviewed: responses are bounded by size, container and widget limits, support ETag revalidation, and return published page data only.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.0
- Approval date
- Nov 8, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- The page-resolution API ships public and rate limited by default; adding authentication is a configuration choice left to the site owner.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
Version history
Showing the 10 most recent of 14 approved releases-
v1.1.0Nov 10, 2026 -
v1.1.0-beta.53Nov 2, 2026 -
v1.1.0-beta.52Oct 28, 2026 -
v1.1.0-beta.51Oct 20, 2026 -
v1.1.0-beta.50Oct 17, 2026 -
v1.1.0-beta.49Oct 10, 2026 -
v1.1.0-beta.47Oct 9, 2026 -
v1.1.0-beta.46Oct 8, 2026 -
v1.1.0-beta.45Oct 8, 2026 -
v1.1.0-beta.44Oct 7, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.