Fernand handles the inbox, the widget, and the knowledge base. Your scripts, n8n, Zapier, Make, or a coding agent add the business logic on top, with a key that only has the permissions it needs.
Included in our $29/human/month transparent pricing
The Fernand API is not a consolation prize for missing integrations. It is how technical teams extend a calm support product without turning it into an enterprise settings maze.
You create a key under Settings → Integrations → API keys. Keys are scoped: read-only, single-purpose, or limited to specific permissions. That shape is what you want when the caller is Claude Code, Cursor, Codex, Gemini, or a coworker agent, not only a trusted backend job.
The same API is what you use from n8n, Zapier, Make, or a small script. Authenticate with the X-Api-Key header, then list conversations, reply, close threads, update the knowledge base, or file a Linear issue. Docs live at developers.getfernand.com. The OpenAPI spec is public.
List, search, read, reply, create, update, bulk-update, or export a conversation. Save a draft. List messages, notes, and events as a single timeline.
Search contacts, update them, manage suppressions, and link or unlink a payment email. Same matching you can do by hand in the inbox.
Search, create, attach, update, and detach issues. An agent can file a bug from a conversation without a human copying the thread into the tracker.
CRUD for articles, collections, and links. Add files, URLs, text, and Q&As to the AI store. Retrain sources. The inbox AI and the widget agent read from the same knowledge.
Create and toggle rulesets. Manage snippets. Read or update custom data configuration and inspect the API logs when an endpoint misbehaves.
Read-only keys for exploration. Single-purpose keys for “only reply” or “only update docs.” Revoke in one click if a key leaks. The blast radius is whatever you scoped.
Create a scoped key, paste the docs, and let the agent list stale conversations, draft follow-ups, or file Linear issues. You still review what you want to review.
When a conversation is tagged “churn,” your scenario can update the CRM, notify a channel, or kick a workflow. Fernand does not need a native connector for every SaaS tool you own.
Close conversations that have been waiting on the customer for a week. Export a PDF. Update a tag. A 40-line script is allowed to be the integration.
The headless API can drive a support experience inside your product. Your UI, Fernand’s inbox behind it.
Email, live chat, Slack, the knowledge base, and AI already live here. The API does not replace that. It lets you script around it.
Refunds in a private admin, seats in Postgres, a special onboarding state: that is your domain. Custom data can display it. The API can act on the conversation when something in your domain changes.
Scoped keys exist because people now hand credentials to coding agents. Give them the smallest key that does the job. Docs: developers.getfernand.com.
API access is included in $29/human/month. There is no extra charge per agent action or API call.
A sample of the surface. The full reference is on the developer site.
Claude Code, Cursor, Codex, Gemini, or any agent that can call HTTP APIs. The prompt tells the agent to read the docs, ask for an account, then create a scoped key.
Full reference at developers.getfernand.com
Straight answers, without the marketplace filler.
Yes. That is a supported way to extend Fernand. Create a scoped API key, point the agent at the developer docs, and let it read or act on conversations within those permissions.
Anything you can do in the Fernand app, you can do with the API.