Quill.dev Authentication

Welcome to the Quill API — a RESTful service for managing notes, notebooks, and tags programmatically. The API lets you build integrations that sync, search, and organize notes from any platform.

Base URL: https://api.quill.dev/v2

All requests must be made over HTTPS. Calls made over plain HTTP will fail. All responses are returned as JSON encoded in UTF-8.

The Quill API uses bearer token authentication. Every request must include an Authorization header containing a valid API key.

Obtaining an API key

1. Sign in to your Quill account at https://app.quill.dev.
2. Navigate to Settings → Developer → API Keys.
3. Click Generate new key, give it a descriptive name, and select the scopes you need (notes:read, notes:write, notebooks:read, notebooks:write, tags:*).
4. Copy the key immediately — Quill only displays it once.

Making an authenticated request

 

GET /v2/notes HTTP/1.1
Host: api.quill.dev
Authorization: Bearer qk_live_8f4c2a1d9e3b7f6a5c8d1e2b4a9f7c3d
Accept: application/json

Keys prefixed with qk_test_ operate against the sandbox environment and never affect production data. Keys prefixed with qk_live_ operate against your real workspace.

Error responses

Status	Code	Meaning
401	invalid_api_key	The key is malformed, revoked, or doesn't exist.
401	expired_api_key	The key has passed its expiration date.
403	insufficient_scope	The key is valid but lacks the required scope for this endpoint.

Never embed live keys in client-side code. If a key is leaked, revoke it from the dashboard immediately — old keys are invalidated within 30 seconds of revocation.