Managed Developer API

Render, diagnose, and manage crawler output from your own workflow.

Use Prerender Buddy through a versioned API when you want managed rendering without operating the browser infrastructure yourself.

Start with Pro Open Markdown reference

Availability

Included on Pro, Agency, and custom plans.

Free and Starter plans can still use the dashboard, public tools, and normal setup flows, but hosted Developer API calls are gated.

Bearer API keys

Create scoped keys in the dashboard and send them server-side.

Shared render quota

Fresh API renders count against the same monthly render allowance as managed crawler rendering.

Cache operations

Purge registered URLs and inspect cache hit, miss, stale, and failure behavior.

Public URL boundary

Internal rendering infrastructure, queues, provider details, and abuse controls stay private.

Authentication

Keep keys out of browser code.

The Developer API is designed for server-side middleware, CI jobs, backend services, and trusted local developer tools.

Example request

curl https://api.prerenderbuddy.com/v1/developer/render \
  -H "Authorization: Bearer pb_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/pricing",
    "includeHtml": true
  }'

Endpoint surface

Small public contract, private engine internals.

The first version focuses on rendering, diagnostics, cache actions, site verification, usage, and logs.

Workspace

GET/v1/developer/sites

List registered sites available to the API key workspace.

GET/v1/developer/usage

Read plan quota, render usage, API requests, cache states, and failures.

GET/v1/developer/logs

Review recent render and Developer API activity.

Rendering

POST/v1/developer/render

Render a registered public URL and optionally return crawler-ready HTML.

POST/v1/developer/diagnostics

Compare raw versus rendered output or extract page signals.

Operations

POST/v1/developer/cache/purge

Invalidate cache for a registered URL.

POST/v1/developer/sites/:id/verify

Check whether a site integration is routing crawler traffic correctly.

Errors and safety

Predictable JSON errors and bounded requests.

Responses include structured error codes and a request ID so failures can be logged and traced.

API keys stay server-side and are shown only once.

Keys can be scoped to render, diagnostics, cache, sites, and usage.

Only public HTTP and HTTPS URLs are accepted.

Private IPs, local hostnames, unsafe redirects, oversized responses, and long-running requests are blocked or bounded.

Machine-readable reference

Agents and scripts can read the Markdown version.

The human page explains the product. The Markdown file gives agents a compact endpoint, error, and security reference.

Open api.md