CiVQ Knowledge Guide
Builders & owners

The Partner API

Third parties (vendors, integration partners, civic-tech developers) can do business with the platform programmatically. Two halves: a self-service developer portal inside the dashboard, and the public API documentation.

…/dashboard/developer-portal
Developer portal — a tenant creates apps, issues/rotates API keys, sets webhook endpoints, and watches usage.
Developer portal — a tenant creates apps, issues/rotates API keys, sets webhook endpoints, and watches usage.
civq.us/api/partner/v1/docs
The live OpenAPI docs (Swagger UI) — every public endpoint, scope, and schema.
The live OpenAPI docs (Swagger UI) — every public endpoint, scope, and schema.
Open the live API docs: civq.us/api/partner/v1/docs  ·  machine spec: openapi.json
  1. Auth — long-lived API keys (shown once, hashed at rest) or OAuth2 client-credentials. Both are tenant-bound and scope-bound.
  2. Scopes — least-privilege per module + action (e.g. service_requests:read, permits:write).
  3. Webhooks — partners subscribe to events; deliveries are signed (HMAC) and retried, with a delivery log.
  4. Limits — per-key rate limits and quotas; tenant isolation is enforced on every call.
CiVQ
Bilingual civic software for local government — own it or rent it.
Product
Products Pricing Why CiVQ Bilingual
Company
About Contact Platform guide API docs
Legal
Privacy Terms Accessibility
© 2026 CiVQ · Pragmatic Business Solutions, LLC — Rio Grande City, TexasKnowledge Guide
×
↑↓ to navigate↵ to openesc to close