EmbedFox documentation
Publishing event direction
The product direction includes signed publishing events for teams that need another system to react when a document changes.
Read the product roadmapWhen an event is useful.
A document workflow may need to update a website, clear a cache or notify another service after a document is published, replaced or disabled. An event lets that system react without polling a reader URL.
What the public contract must make clear.
A public event contract needs a signed request, a stable event identifier and safe retry behaviour. It must also describe how the receiver can ignore a repeated delivery.
Public boundary. The public reader, source PDF and account data are not event payloads. A delivery event should identify only the document change the receiving system needs to handle.
Questions this page answers.
Short answers to what publishers ask about this part of EmbedFox.
- Can my system get an event today?
- No. Signed publishing events are direction, not a contract you can build against yet.
- What would an event contain?
- Enough to identify the document change a receiver has to handle. Never the reader HTML, the source PDF or account data.
- What has to be true before events open?
- A signed request, a stable event identifier, safe retries and a documented way for a receiver to ignore a repeated delivery.
Keep reading.
Where publishers usually go next from here.