Public API
Feedjolt's REST API uses JSON and Bearer-token auth. Read and write posts, comments, votes, statuses, and more. Full interactive reference at api.feedjolt.com/docs.
The Feedjolt API is a REST API over JSON. Auth is via API keys (Bearer tokens). The full endpoint reference, with try-it, is at:
This page covers what you need to know before opening that. Engineer-oriented detail (auth, errors, pagination, idempotency, webhook contract) is in Developers -> API.
Base URL
https://api.feedjolt.com/api/v1Authentication
- Dashboard -> Settings -> API keys -> New key.
- Pick a name (something like
production-zapierso you remember). - Pick scopes - what the key can do.
- Copy the key. It's shown once. If you lose it, you'll need a new one.
Send the key in the Authorization header:
Authorization: Bearer fjk_abc123...API keys start with fjk_ so they're easy to spot in logs (and in our git-leak detection).
What you can do
The API exposes the same operations the dashboard performs - read and write posts, comments, votes, statuses, tags, members, webhooks. Per-endpoint detail (path, body shape, query params, response schema, scopes required) is in the OpenAPI reference.
A typical call:
curl -H "Authorization: Bearer $FEEDJOLT_KEY" \
"https://api.feedjolt.com/api/v1/boards/feature-requests/posts?limit=10"Errors
Errors return standard HTTP codes (400, 401, 403, 404, 409, 422, 429, 5xx). Bodies follow FastAPI's default shape. Every response includes an X-Request-ID header - include it in any bug reports.
See Developers -> API -> Errors for retry strategy.
Revoking keys
Keys can be revoked at any time at Settings -> API keys. Revocation is immediate.
If a key is leaked, revoke it immediately. We don't auto-detect leaks (yet); we recommend git-secrets or a similar pre-commit hook.
OpenAPI spec
Full reference, interactive, with try-it:
The OpenAPI JSON is at https://api.feedjolt.com/openapi.json for codegen.
SDK / clients
We don't ship official SDKs yet. The API is small enough that a hand-written client in your language of choice is usually fine. If you write one, send it our way and we'll list it here.
Webhooks
Feedjolt POSTs signed events to your endpoint when posts, statuses, comments, or votes change. Set up endpoints, pick events, and replay from the delivery log.
Developers
Integrate Feedjolt into your app with the embeddable widget, signed webhooks, and the REST API. Quickstart, references, and the bug-reporting workflow.