Connect your notes to AI and automation.

Quick start

1. Sign in and open Settings → API keys.
2. Create a named key and copy it immediately. It is shown only once.
3. Store it in your AI tool's protected secret or authorization setting.
4. Test the connection with GET /api/me.

Verify your key

curl https://dailysync.apercallc.com/api/me \
  -H "Authorization: Bearer ds_live_YOUR_KEY"

Use it with your AI

Example request

Review my DailySync note for today. Suggest a concise standup,
but ask me before writing changes. Preserve existing blockers.

The AI product must support authenticated HTTP actions, tools, or connectors. Never paste the key into a normal chat unless the product explicitly treats that field as a protected secret.

Endpoints

List recent notes

curl "https://dailysync.apercallc.com/api/notes?limit=30" \
  -H "Authorization: Bearer ds_live_YOUR_KEY"

Results are newest first. When hasMore is true, request the next page with ?before=nextBefore. Use ?since=2026-07-21T12:00:00.000Z for incremental synchronization.

Create or update a note

curl -X PUT https://dailysync.apercallc.com/api/notes/2026-07-21 \
  -H "Authorization: Bearer ds_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"yesterday":"Shipped onboarding","today":"Finish API docs","impediments":[],"actionItems":[],"todayPriority":"normal"}'

For an update, read the note first and send its revision as baseRevision. HTTP 409 means another device changed the note; merge deliberately instead of retrying blindly.

JavaScript example

const response = await fetch(
  "https://dailysync.apercallc.com/api/notes?limit=7",
  { headers: { Authorization: `Bearer ${process.env.DAILYSYNC_API_KEY}` } }
);
if (!response.ok) throw new Error(`DailySync: ${response.status}`);
const { notes } = await response.json();

Keep the key on a server, in a secret manager, or in a protected automation credential. Never expose it in client-side JavaScript.

Responses and limits