API-first / headless

Pull ContentPulse articles into your Laravel app.

Run your own frontend? ContentPulse is API-first. Connect your Laravel application with an API key, listen for a webhook, and render ready-made article HTML in your own Blade views — 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 four steps

STEP 1

Create an API key

In ContentPulse, go to Settings › API Keys and create a key for your site. Store it in your Laravel .env.

STEP 2

Register a webhook

Add a webhook in ContentPulse pointing at your app (e.g. /webhooks/contentpulse) subscribed to content.published. We sign every delivery so you can verify it’s us.

STEP 3

Fetch the article

When the webhook fires, call our REST API with your key (X-API-Key header) to fetch the article: title, slug, SEO meta, image URL, FAQ pairs, and pre-rendered HTML.

STEP 4

Render in your Blade view

Store the payload and output {!! $article->rendered_html !!} in your view. The HTML is self-contained and theme-neutral — it inherits your typography and styles.

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