EmbedFox documentation
Publishing API direction
The product direction includes a publishing API for teams that prepare documents in other systems and publish them on their own website.
Read the product roadmapWhat the API is for.
A publishing API belongs between the source of a document and the place where readers open it. It should create or update a document, set the title and language, and return a reader or embed destination without exposing an owner credential in a browser.
What a reliable integration needs.
The product direction covers repeat-safe requests, clear quotas and signed event delivery. Those details matter when an automated job retries or when a document is replaced under an existing public link.
Public boundary. The public upload flow does not require an API: upload a public PDF, then use its reader link or embed snippet. API documentation will name endpoints and credentials only when they are part of the public product.
Questions this page answers.
Short answers to what publishers ask about this part of EmbedFox.
- Is there an API I can use today?
- No. There is no public API contract and no API key. Publishing works without one: upload a PDF, then use its reader URL or embed snippet.
- How do I integrate in the meantime?
- The versioned embed snippet is the stable integration point. It needs no credential and keeps working as the product changes.
- When will the API open?
- When repeat-safe uploads, quotas, rate limits and signed events are in place. The roadmap tracks that; nothing is promised before it is live.
Keep reading.
Where publishers usually go next from here.