Our API has two paths. Most people use the Rendered API, which returns fully rendered HTML built with your DropInBlog layout, ready for SEO with little frontend work. Use the Raw API when you want structured JSON and full control over UI, routing, and rendering.
| Rendered Output | Raw Data | |
|---|---|---|
| What you get | Fully built, production-ready HTML | Structured JSON content |
| Frontend work | None required | Build templates or components |
| Setup speed | Fast | Flexible, but requires more work |
| Updates | Automatic updates and improvements | Manual updates and improvements |
| Best for | Low-maintenance blogs with minimal setup | Custom designs and full control |
Authentication
Our API supports OAuth 2 integration, providing a secure and standardized method for authenticating and authorizing users. There are two types of API keys...
- Private: Private keys are designed for creating and updating posts, and can not be used to display a blog on your website. Employing them on your frontend poses a security risk.
- Public: Public keys are used to render your blog on your website.
You can manage your OAuth tokens in your DropInBlog account.
Rate Limits
The default rate limit is 60 requests per minute. Exceeding the rate limit will result in a HTTP 429 error requesting you slow down the rate you are making requests at.
Every request has two rate limit related response headers.
| Response Header | Description |
|---|---|
| x-ratelimit-limit | Contains the current overall rate limit per minute |
| x-ratelimit-remaining | Contains the number of available requests remaining in the current minute |