The Quackback REST API gives you full programmatic access to every resource: posts, votes, comments, boards, tags, users, and changelogs. The API follows REST conventions with JSON request and response bodies, cursor-based pagination, and clear rate-limit headers. An OpenAPI 3.0 specification is available at /api/v1/docs for client generation in any language. Authentication uses API keys for server-to-server calls and OAuth for user-facing apps. Developers can build custom feedback widgets embedded in their product, internal dashboards that aggregate feedback metrics, or scripts that automate triage and categorization. Everything the Quackback UI can do, the API can do.
Connect REST API to Quackback in three steps.
Create an API key in your Quackback project settings. Use it in the Authorization header for server-to-server requests.
Visit /api/v1/docs to browse endpoints, request schemas, and response examples. Generate a client library or test calls directly.
List posts, create votes, update statuses, and manage boards programmatically. All list endpoints support cursor-based pagination.
Use the API to build a feedback widget inside your application. Users submit requests and vote without leaving your product, and the data flows into your Quackback board for the product team to manage.
The /api/v1/docs endpoint serves an OpenAPI 3.0 specification. Generate a typed client in TypeScript, Python, Go, or any language your team uses. No manual HTTP calls needed.
Write scripts that read new posts, apply tags based on keyword matching, assign statuses, or merge duplicates. The API supports every CRUD operation, so any manual workflow can become an automated one.
Full CRUD operations on all resources
OpenAPI 3.0 specification at /api/v1/docs
API key and OAuth authentication
Rate limiting with clear headers
Build custom feedback widgets embedded in your product
Create internal dashboards with feedback metrics
Automate feedback triage with custom scripts
Step-by-step instructions to connect REST API with Quackback.
Yes. Rate limits are applied per API key with clear headers indicating remaining requests. Limits are generous enough for most use cases, and custom limits can be configured for self-hosted instances.
All list endpoints support cursor-based pagination with configurable page sizes, making it easy to fetch large datasets efficiently.
Deploy Quackback and connect REST API in minutes. Free forever on your own infrastructure.