Fresh Jots for developers

What Fresh Jots is — and isn't

Fresh Jots is the place to store digest outputs from your jobs — successful payments one after another, errors, failed deploys, daily summaries, AI session transcripts — anything you'd actually want to read on your phone. Raw firehose server output? Pipe it into a log aggregator (Datadog, BetterStack). Fresh Jots is the everyday highlights layer above that, plus any note you'd like to write by hand. Append-only mode protects accidental overwrites for log-style notes.

The pitch

Most notes apps want you to file things into a hierarchy. Fresh Jots' Dev tier inverts that for the engineering use case: the note is the channel. Closer to "Slack channels for bots" than "fancy notes app." A few examples of what people actually wire up:

• claude-code — sublimate AI coding sessions via a slash command
• cron-jobs-prod — hourly cron one-liner with the result
• payments-product-X — Stripe webhook handler appends each event
• failed-deploys — GitHub Action on red writes a one-liner
• engineering-journal — shell alias j "fixed the auth bug"
• agent-scratchpad — autonomous-agent working memory between runs

One curl, one event

Two patterns. Append-only for log streams; standard CRUD for editable notes.

Sending the bearer token — two ways:

A. Export it once, then reference it as $MYNOTES_API_TOKEN in any curl in the same shell session:

export MYNOTES_API_TOKEN="mn_yourrealtokenhere"

curl -X POST https://freshjots.com/api/v1/notes/by-filename/cron-jobs-prod/append \
  -H "Authorization: Bearer $MYNOTES_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text":"backup ok 2026-04-26 03:00"}'

B. Paste the raw token inline — no $. Fine for one-off testing; the token will sit in your shell history, so rotate it after:

curl -X POST https://freshjots.com/api/v1/notes/by-filename/cron-jobs-prod/append \
  -H "Authorization: Bearer mn_yourrealtokenhere" \
  -H "Content-Type: application/json" \
  -d '{"text":"backup ok 2026-04-26 03:00"}'

The endpoint examples below use option A. The $MYNOTES_API_TOKEN in them is a shell-variable reference — leave the $ in. Replacing the variable name with your literal token (e.g. $mn_realtoken) breaks the request because bash interprets $mn_realtoken as a different (undefined) variable.

Append-only by filename — first call creates the note, every subsequent call adds a line. No id lookup, no setup step:

curl -X POST https://freshjots.com/api/v1/notes/by-filename/cron-jobs-prod/append \
  -H "Authorization: Bearer $MYNOTES_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text":"backup ok 2026-04-26 03:00"}'

cron-jobs-prod is just an example — pick any filename; it becomes the note's title and how it's shown in Fresh Jots.

Standard CRUD note — POST to create, PATCH to edit, DELETE to remove:

curl -X POST https://freshjots.com/api/v1/notes \
  -H "Authorization: Bearer $MYNOTES_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"note":{"title":"Q4 plan","plain_body":"Top priorities..."}}'

Idempotency keys protect against double-writes on retries. The bulk endpoint lets you ship up to 50 notes per request. Full API docs at /docs.

What you get on Pro / Team

Every successful response carries X-RateLimit-* headers; 429s carry Retry-After. Per-user API error log shows every 4xx your tokens have hit. Full caps and rate limits at /limits.