API changelog

This page lists every change to the Pepvote API. Changes are additive: new fields, values, and endpoints appear here when they ship, and nothing existing changes shape without notice. Anything that will change behaviour for existing integrations is announced under Upcoming changes first, with a date.

Check this page before you upgrade an integration. For the full reference, see the API overview.

Upcoming changes

No upcoming changes.

September 2026

• Launched the Pepvote API at https://api.pepvote.com with bearer API keys created under Profile → API keys. Keys carry read or read and write scopes.
• Added read and write endpoints for voting events, positions, candidates, groups, and voters, including a batch voter create endpoint of up to 100 rows per request.
• Added read endpoints for sponsors, event stats, results, and votes. Listing votes requires a plan with data export.
• Added webhook endpoint management so automation platforms can subscribe to events over REST.
• Added GET /health for uptime monitoring and GET /me for connection tests.
• Added an unauthenticated GET / that returns the company name, website, api_doc, and status links, plus GET /docs and GET /docs/<page> redirects into these pages.
• Added cursor pagination, a uniform error envelope, per-key rate limits with X-RateLimit-* headers, and Idempotency-Key support on POST requests.