Troubleshooting

Find and fix embed problems, from error codes in the browser console to docs that don't appear or users who can't see private pages.

Start in your browser's console. The embed logs every problem there as [DocumentationAI] message (code), and fires the error event with the same code.

Error codes

Code	What it means	How to fix it
`origin_not_allowed`	The page's origin isn't one of the key's allowed origins.	Add the exact origin, including its port, in Settings > Embed with Edit. Changes apply within a few minutes.
`publishable_key_invalid`	The key is mistyped, revoked, or belongs to another docs site.	Copy the key again from Settings > Embed. If it was revoked, create a new key.
`publishable_key_expired`	The key's expiry date has passed.	Create a new key. Expiry can't be extended.
`invalid_token`	The reader token was already used, is more than 60 seconds old, was mistyped, or was made with another embed key. On JWT sites, the JWT failed verification.	Get a new token for every `identify()` call, and make sure your token endpoint's response isn't cached.
`sign_in_not_enabled`	`identify()` was called, but the docs site has no sign-in.	If your docs are public, remove the `identify()` call. Otherwise set up Access Control.
`auth_method_unsupported`	A JWT was passed on a site that doesn't use JWT sign-in.	Use a reader token.
`site_not_found`	Your docs site couldn't be found at its address.	Check that your docs are published. On a subpath, check your proxy setup.
`unexpected_error`	Something else, such as a network failure.	Check your connection and your Content Security Policy.

Common problems

Still stuck?

Next steps

Reference

Every option, method, event and Content Security Policy rule.

Private docs

Sign users in to your private pages.

Was this page helpful?