The Political Comms API.

One REST surface for every step of a political messaging program. Send, register, verify, export, and report. OpenAPI 3.1 spec published and current.

Open the reference Developer hub

Base URL

api.politicalcomms.com/v1

Auth header

X-API-Key

Spec

OpenAPI 3.1

Versioning

URI /v1

REST API

Projects, contact lists, media, brands, campaigns, phone numbers, tracking domains, analytics, and billing. Every surface is documented in the API reference.

Browse endpoints

Webhooks

Subscribe to message.sent, message.delivered, message.failed, message.replied, and link.clicked. HMAC-signed with automatic retry.

Webhook reference

Authentication

API keys are passed in the X-API-Key header. Keys are prefixed pc_live_, generated from the dashboard, and shown once.

Auth model

Rate Limits

100 requests per hour per API key. Response headers tell you where you stand. Idempotency-Key headers are supported on writes.

Limits and retries

Machine-readable spec.

The OpenAPI 3.1 file is live and current. Point your generator at it and run.

GET docs.politicalcomms.com/api-reference/openapi.json

Ready to integrate?

Talk to engineering. Most accounts are provisioned and live inside 48 hours, with a real human walking you through brand setup, registration, and your first project.

Get API access Developer hub