Getting the most out of the Whale API
You probably already know Whale as the home for your team's knowledge, SOPs, and training. But did you know there's a whole layer underneath that you can plug into? That's our API — and it lets Whale talk to the other tools you use every day.
This article is a high-level tour of what's possible. We'll skip the technical deep-dive and instead focus on the why: what kinds of problems you can solve, and what becomes possible when you connect Whale to the rest of your stack — including AI assistants like Claude or ChatGPT.
Heads up: API access is only available on our Enterprise plan. If you're not sure whether your current license includes it, just reach out to your Customer Success contact or our support team and we'll point you in the right direction.
What is the Whale API, in plain English?
Think of the Whale API as a side door into your Whale account. Through that door, other software can read information from Whale, send information back, or trigger actions — all without anyone having to log in and click around manually.
In practice, that means:
Pulling cards, content, or training data out of Whale and using it somewhere else
Pushing new content, users, or updates into Whale from another system
Keeping Whale automatically in sync with the tools your team already relies on
You don't have to build something massive. Even small connections — like automatically adding new hires to Whale when they're added to your HR system — can save hours every week.
What you can actually do with it
Here's a sense of the kinds of things our customers explore once they get API access. This isn't an exhaustive list — it's a starting point.
Keep your team list in sync automatically
When someone joins, moves teams, or leaves, you want Whale to reflect that quickly. With the API, your HR or identity system can update Whale automatically — new users get access on day one, leavers are removed without anyone having to remember.
Pull reporting into your own dashboards
If you already have a BI tool (Power BI, Tableau, Looker, a custom dashboard), you can feed Whale data into it. Things like training completion, engagement on cards, or onboarding progress can sit alongside the rest of your operational metrics.
Trigger Whale actions from other tools
Imagine a new client is added in your CRM. With a small workflow in something like Zapier, Make, or n8n, that event can automatically assign the right onboarding playbook in Whale. No manual handoff needed.
Bring Whale content into other apps
Some teams want their SOPs visible right inside the tool where the work is happening — a help widget on an internal portal, a sidebar in a custom app, or a quick reference inside a support tool. The API lets you fetch the right Whale content and display it where your team already is.
Keep content fresh from the source
If your "source of truth" for something lives elsewhere — pricing in a database, product specs in a PMS, policies in a compliance tool — you can use the API to keep the matching Whale cards updated automatically, so your team is never reading stale info.
Connecting Whale to AI assistants like Claude or ChatGPT
This is one of the more exciting things our customers are starting to experiment with, so it's worth its own section.
Modern AI assistants are great at answering questions in natural language — but they only know what you give them. If you give Claude or ChatGPT access to your Whale content (through the API), suddenly the assistant can answer questions based on your company's actual processes and policies, not just generic knowledge from the internet.
A few realistic examples:
Drafting and updating content. Going the other direction, an AI assistant can help you draft new SOPs, summarize long documents into Whale cards, or suggest improvements to existing ones — using Whale's API to pull in what already exists so the new content stays consistent.
Smart automations. Combine an AI assistant with the API and a workflow tool, and you can do things like: when a manager describes a new process in a Slack message, have the assistant turn it into a structured Whale card draft for review.
The technical glue varies (some teams build this themselves, others use platforms like Zapier, Make, n8n, or custom MCP setups), but the idea is the same: your knowledge, made conversational.
A few things worth knowing
API access depends on your plan. Not every license tier includes it, and that's intentional — it's a more advanced capability. We're happy to talk through whether it's the right fit.
Security matters. API access uses secure authentication, and we recommend treating your API credentials with the same care as a password. Anyone building an integration should follow standard security practices (don't share keys in chat, rotate them, etc.).
We're here to help with the "what," not the "how." Our team can help you understand what the API can and can't do, and what's a good use case. The actual building is done by your developer or integration partner.
Got an idea? Let's talk.
If you're reading this and thinking "I think we could automate X with this" — that's exactly the right instinct. Reach out to support or your Customer Success contact, tell us what you're trying to achieve, and we'll help you figure out whether the API is the right tool and what your next step should be.
The most interesting integrations almost always start as a small "what if" conversation. We'd love to have that conversation with you.