Skip to content

FYInbox docs

Deduplication and retries

Give each logical event a stable source-scoped key so a network retry cannot create a second inbox item while the original is retained.

Build a stable key

Derive deduplicationKey from immutable event identity, not the retry attempt or current time. Useful shapes include deploy:<service>:<commit>, run:<workflow>:<run-id>, and invoice:<invoice-id>:paid. The same string may be reused by another source because uniqueness is scoped to the source selected by the API key.

What a duplicate means

  • The first accepted request returns 201 and created: true.
  • A repeat returns 200, created: false, and the original notification id.
  • The service does not compare the repeated payload with the original payload.
  • The guarantee lasts while the original notification exists; retention can eventually permit the key to create a new item.