Does the producer need a special integration?

No. The examples use an authenticated HTTPS request, so any script, service or visual workflow that can send HTTP can use the same contract.

Should credentials be included in notification data?

No. Keep credentials in the producer's secret store and send only the context needed to understand or locate the event.

Why send this to FYInbox instead of chat or email?

FYInbox gives project notifications one structured, reviewable home instead of scattering them through Slack, Telegram and email. Those tools remain useful for conversations and intentional messages.

Why structure notifications for people and agents?

People and agents both need stable source, outcome and next-action context. FYInbox keeps that context in one notification record outside conversation streams.

Guide

Send your first notification with curl

The shortest path from a project to FYInbox is an API key and a POST request. The result becomes one structured notification for people and agents instead of another chat message.

Updated Sep 3, 20265 min read

Keep the source key outside the command

Create a source
Open the inbox onboarding flow, name the producer and create a revocable key for that source.
Store the key
Put the once-visible value in your shell or deployment secret store as FYINBOX_API_KEY.

POST the event

Send a backup completion event

curl --fail-with-body \
  --request POST \
  --url "$FYINBOX_URL/api/v1/notifications" \
  --header "Authorization: Bearer $FYINBOX_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"title":"Backup completed","body":"Nightly PostgreSQL backup finished and passed restore verification.","severity":"success","source":"backup-worker","tags":["backup","production"],"deduplicationKey":"backup:2026-07-31","metadata":{"duration":"42s","size":"1.8 GB"},"actions":[{"id":"open-backup","type":"link","label":"Open backup","href":"https://example.com/backups/2026-07-31","style":"primary"}]}'

A successful request returns the notification identifier and whether a new record was created. Reusing the same deduplication key returns the existing record instead of creating another inbox item.

Primary sources

Last verified Sep 3, 2026.

Frequently asked questions

Does the producer need a special integration?: No. The examples use an authenticated HTTPS request, so any script, service or visual workflow that can send HTTP can use the same contract.
Should credentials be included in notification data?: No. Keep credentials in the producer's secret store and send only the context needed to understand or locate the event.
Why send this to FYInbox instead of chat or email?: FYInbox gives project notifications one structured, reviewable home instead of scattering them through Slack, Telegram and email. Those tools remain useful for conversations and intentional messages.
Why structure notifications for people and agents?: People and agents both need stable source, outcome and next-action context. FYInbox keeps that context in one notification record outside conversation streams.

GuideSend cron job notifications from Bash GuideDeduplicate notifications from retried jobs GuideStructure metadata, tags and notification actions Use caseReview cron jobs and backup results in one inbox

Put project notifications in their own inbox

Create an account and move the next notification out of chat and into one inbox for people and agents.

Create account