Developer Docs, SDKs, and API
This article gives a high-level overview of the DropInBlog SDKs and APIs you can use to integrate blogging functionality into your applications. We provide several open-source packages for different environments, along with two main APIs tailored to your needs.
Table of Contents
﹂ Main API
Rendered Output vs Raw Data
| [[rendered]] Rendered Output | [[raw]] Raw Data |
|---|---|---|
What you get | Fully built, production-ready HTML | Structured JSON content |
Frontend work | None required | Build templates or components |
Setup speed | Fast | Less fast, more flexible |
Updates | Automatic updates and improvements | Manual updates and improvements |
Best for | Low-maintenance blogs with minimal setup | Custom designs and full control |
Overview
DropInBlog offers flexible tools to integrate DropInBlog into your applications. Depending on your stack and whether you need server-rendered HTML or client-side rendering, you can choose between packages optimized for:
- Laravel
- React frameworks (generic, Next.js, Express)
- REST APIs for raw data or rendered HTML
Packages
Below is a brief explanation of each of our SDKs.
Laravel [[rendered]]
Repository: https://github.com/DropInBlog/laravel-rendered
A Laravel package that fetches pre-rendered HTML from DropInBlog’s Rendered API and injects it directly into blade views.
React Core [[rendered]]
Repository: https://github.com/DropInBlog/react-core
React Core is the foundational React library for DropInBlog. It provides reusable hooks and components to fetch blog data from the Rendered API.
React Next.js [[raw]]
Repository: https://github.com/DropInBlog/react-nextjs
React Next.js comes with pre-configured components and utilities optimized for Next.js applications.
React Express [[raw]]
Repository: https://github.com/DropInBlog/react-express
A React + Express boilerplate that combines React SSR with an Express server. It's useful when your app architecture blends React with backend routed content.
APIs
DropInBlog exposes two main APIs: one for raw JSON data and one for pre-rendered HTML.
The SDKs and framework packages above are built on top of these APIs and provide more convenient, native ways to work with them.
Main API [[raw]]
Reference: https://dropinblog.readme.io/reference/api-reference
The primary REST API for retrieving blog content in structured JSON. Use this when:
- You want complete control over your blog’s UI and routing. You are responsible for rendering content, defining routes, and shaping the user experience to fit your application.
- You want to create and update posts programmatically.
Rendered API [[rendered]]
Reference: https://dropinblog.readme.io/reference/rendered-introduction
The Rendered API returns fully rendered HTML for blog pages. This is ideal when:
- You want a quick and simple integration without custom UI work.
- You want server-ready SEO content.
Updated on: 09/01/2026