API
API keys are available on every plan (they authenticate the MCP server and any tool). The programmatic REST API documented below —
POST /api/v1/decks— additionally requires the Scholar plan.
The Flipnem API lets AI agents, scripts, and external tools create decks and their cards programmatically — no browser required. It is a one-shot call analogous to the Hashcard Markdown file import available from the Create Deck dialog.
API Keys
Keys are managed in Settings → API Keys:
- Create keys with custom labels
- Up to 10 keys per account
- Each key can be revoked independently
- The raw key value is shown once at creation — store it somewhere safe
Keys start with fnem_ and are passed as a Bearer token on every request:
Authorization: Bearer fnem_your_key_here
Keys work on every plan for the MCP server. The programmatic REST API (POST /api/v1/decks) additionally requires Scholar — on the Learner plan those calls return 403.
Lost or Exposed Keys
There is no way to retrieve a key after it has been created. If you lose a key or believe it has been exposed, revoke it from Settings → API Keys and create a new one. Update any integrations with the new key before revoking the old one to avoid downtime.
Creating Decks
Create a deck and populate it with cards in a single request.
Endpoint: POST /api/v1/decks
curl https://flipnem.com/api/v1/decks \
-H "Authorization: Bearer fnem_your_key_here" \
-H "Content-Type: application/json" \
-d '{
"name": "US State Capitals",
"content": "Q: Alabama\nA: Montgomery\n\nQ: Alaska\nA: Juneau"
}'
Cards use the Hashcards format — separate cards with a blank line (\n\n). Maximum 500 cards per request.
OpenAPI Schema
A machine-readable schema is available at:
https://flipnem.com/api/openapi.json
Use this with tools like Cursor, GPT Actions, or any OpenAPI-compatible client to get auto-completion and type-safe requests.
Workflow Example
Paste source material into an AI assistant and ask it to call POST /api/v1/decks directly — the deck lands in your library in seconds. For interactive deck building, card management, and AI-driven review sessions, use the MCP server instead.