Renewr APIPatent annuity management, programmatically.

The Renewr External API v2 lets you read your patent portfolio, review upcoming renewals and their fees, send renewal instructions, and reconcile invoices, all from your own systems.

Get started

API Reference

Migrating from v1?

📅

Renewal events

Pull everything falling due in a given window across your whole portfolio, with estimated fees inline, and know exactly which events you can act on.

The monthly cycle

✅

Instructions

Tell Renewr what to do for each annuity (proceed, skip this occurrence, or drop the patent) and get an instruction receipt back, instantly.

How instructions work

💶

Fees & invoices

A single self-describing fees object from estimate to invoice, with a typed cost breakdown, decimal-string amounts, and optional exchange-rate freezes.

Fees & FX

🧾

Documents

Download invoices, instruction receipts and official payment receipts as PDF, straight from the event they belong to.

Downloading documents

A 60-second look

Authenticate every call with your API key, then walk the resources:

bash

# What falls due in October, with estimated fees?
curl "https://api.renewr.example/api/v2/external/patent-events?dueMonth=2026-10&include=fees" \
  -H "x-api-key: $RENEWR_API_KEY"

# Instruct: renew this annuity.
curl -X POST "https://api.renewr.example/api/v2/external/patent-instructions" \
  -H "x-api-key: $RENEWR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "instructions": [ { "eventId": "9f0d1e7a-3b2c-4d5e-8f6a-7b8c9d0e1f2a", "decision": "PROCEED" } ] }'

Every response carries an X-Request-Id correlation header, RateLimit-* quota headers, and errors are uniform RFC 9457 application/problem+json with stable, machine-readable codes.

Looking for ready-made answers ("I want an estimate for the next three months, how?"): browse the Cookbook.

Access