mocop
Browse · Docs · Guide · Analyze

pdfs.build API

API by pdfs.build · rest

All requests are authenticated with an organization-scoped API key (prs_...) sent as a Bearer token. Create keys under Developer tools → API keys (/developers/api-keys) in the dashboard or with the MCP create_api_key tool. Keys are shown once. The organization in every /v2 URL must match the key's organization, otherwise the request fails with 403 organization_scope_mismatch. Errors are JSON with a top-level error string — a machine-readable code for most failures, a phrase for a few legacy ones — usually alongside a human-readable message. Data validation and template compilation failures carry details / diagnostics instead of a message. Versions. /v2 addresses templates by an external id you control. The legacy /v1 routes identify templates by their generated internal id and remain supported for existing integrations. Timestamps. Objects served by the render service (templates, render jobs, logs, webhook endpoints) carry UTC timestamps in…

Endpoint: https://api.pdfs.build/

Verification: observed. Source: crawl.

Capabilities (44)

  • List render logs (v1)
  • Get render log (v1)
  • Render PDF (v1)
  • List templates (v1)
  • Create template (v1)
  • Get template (v1)
  • List render logs for a template (v1)
  • Publish template (v1)
  • Unpublish template (v1)
  • Get render batch
  • List delegated grants
  • Revoke delegated grant
  • Mint connect ticket
  • Revoke embedded editor session
  • List gallery designs
  • Preview a gallery design
  • List render logs
  • Get render log
  • Get render job
  • Download async render
  • List templates
  • Create template
  • Add a gallery design to the organization
  • Get template
  • Rename external id or set tenant scope
About · Contact · Privacy