Skip to main content

Overview

The embed system lets you display a fully rendered, read-only Pathway book inside an iframe in your own app. Your users don’t need API credentials. The embed token handles access. Flow:
  1. Use your PAT to create an embed token for a book
  2. Drop the token into the iframe URL
  3. Done your users see the live financial report

Create an embed token

book_id
string
required
UUID of the book to embed.
permanent
boolean
default:"false"
If true, the token never expires. Default tokens expire after 24 hours. Use permanent: true for landing pages or persistent embeds.
Response
expires_at is null for permanent tokens, or an ISO timestamp for 24-hour tokens.
One token per book. If a valid token already exists for the book, the same token is returned.

Embed in an iframe

Query parameters
theme
string
light or dark. Defaults to dark if not specified.

Embed routes

Two pages are available for embedding: The same token works for both routes.

Security

Embed tokens are read-only. All write operations (upload, parse, edit) are blocked at the server the token cannot be used to modify anything. The token is also scoped to a single book, so it cannot access other books in your org.

Get embed book data (API)

If you want to fetch the book data programmatically without an iframe, use the public endpoint. No auth header required the token in the URL is sufficient.
This is the same endpoint the iframe uses internally.

Validate a token

Check whether an embed token is still valid.