API-first / headless

Pull ContentPulse articles into your Laravel app.

Run your own frontend? ContentPulse ships an official Laravel package. Connect in one click from your dashboard, install the package, and articles appear on your site automatically, your routes, your design, your domain.

Get started free View on GitHub See pricing

Official package: composer require contentpulseio/laravel, or use the plain REST API from any framework.

Set up in three steps

STEP 1

Connect from your website settings

Open your website in the ContentPulse dashboard, go to Settings › Integrations, and click Connect on the Laravel card. Enter your app URL and we generate your API key and webhook automatically.

STEP 2

Install the package

Run composer require contentpulseio/laravel and php artisan contentpulse:install. Add the API key and webhook secret from the Connect step to your .env.

STEP 3

Publish and go live

The package handles webhooks, syncing, and rendering out of the box. Publish an article in ContentPulse and it appears on your site automatically at your chosen route prefix.

ADVANCED

Customise views & styling

Run php artisan vendor:publish --tag=contentpulse-views to publish Blade templates. Override the layout, styles, and partials to match your brand. The rendered HTML is self-contained and theme-neutral.

What the API gives you

Pre-rendered article HTML

Every article ships with rendered_html (clean, semantic markup with no framework classes) so you store it and print it. No section parsing or recipe logic on your side.

Full SEO payload

Meta title, meta description, slug, keywords, and the hero image URL come in the same response, ready to drop into your layout’s <head>.

FAQ data for JSON-LD

Question/answer pairs are extracted into a structured faq array so you can emit FAQPage JSON-LD and target rich results.

Signed webhooks

Get notified on content.published, content.updated, and more. Each delivery is HMAC-signed so your endpoint can verify authenticity.

Refresh-aware by design

When ContentPulse refreshes an article, you receive an update webhook with the same identifiers, update your stored copy in place and the URL never changes.

Your links, your domain

Set your resource center URL and internal links inside articles are rewritten to your own domain before they reach the API, no ContentPulse URLs leak into your site.

Common questions

No, it’s a plain REST API with JSON responses and webhooks, so any stack works: Symfony, Rails, Django, Next.js, or a static site generator. Laravel is simply where most of our headless customers run.

No. The API returns pre-rendered, self-contained HTML for the article body. You wrap it in your own layout and typography; headings, lists, images, FAQs, and callouts are already structured.

Subscribe to the content webhooks. On content.published or content.updated, fetch the article by its ID and upsert your local copy. Slugs and IDs are stable across refreshes.

Yes, generously for this use case: standard reads are 60 requests/minute per key. A typical publish-sync uses one webhook and one fetch per article.

Your frontend, our editorial workflow. Wire them together in an afternoon.

Get started free Talk to us