Saltar al contenido

Embed SDK

Allowed sites and security.

Only the sites you allow can frame your interviews, and the host page never sees the candidate's sign-in.

Última actualización: 19 de noviembre de 2026

La documentación para desarrolladores solo está disponible en inglés.

Allowed sites

Integrations → Embed holds your company's list of allowed sites: origins like https://careers.example.com (https, no path), up to 20. Adding sites needs a paid plan; emptying the list is always possible.

What the interview pages send

HeaderValue
Content-Security-Policyframe-ancestors with your allowed sites, or 'none' when the list is empty
Permissions-Policymicrophone, camera and display-capture for the page itself and your allowed sites

So a browser refuses to show your interview in a frame anywhere else, and only your allowed sites can pass the microphone on to it.

What your page must allow

A frame can only use what the page around it may use. If your page sends a Permissions-Policy, it must allow microphone, camera, display-capture and screen-wake-lock (a phone's screen stays on during the interview) for the interview's host: the one in your invitation links, https://interview.testee.ai or your company's own https://<company>.testee.ai. A page that turns them off (microphone=()) turns them off in the frame too, and the candidate's microphone check fails with no other sign why.

Response header
Permissions-Policy: microphone=(self "https://interview.testee.ai"), camera=(self "https://interview.testee.ai"), display-capture=(self "https://interview.testee.ai"), screen-wake-lock=(self "https://interview.testee.ai")

If your page sends a Content-Security-Policy, add the interview's host to frame-src (the frame) and to script-src (the SDK script loads from it), and give the inline snippet that mounts the interview your page's nonce.

Response header
Content-Security-Policy: frame-src https://*.testee.ai; script-src 'self' 'nonce-<your nonce>' https://interview.testee.ai

Messages

  • The interview posts events only to the origin your page was loaded from, never to any page, and only when that origin is on the allowed list.
  • The SDK accepts only messages from its own iframe and the interview's origin.
  • Events carry ids, never tokens or personal data.

Sign-in inside the frame

The candidate signs in inside the iframe, with the one-time code emailed to the address they were invited at. Your page never sees the code or the candidate's session. Browsers block third-party cookies in frames, so the session lives in memory: after a reload the candidate signs in again from the link. When your page already signed the candidate in, create the invitation with skipSignIn: true (API › Invitations) and the link alone signs them in: keep its expiry short, since the link is then the only key.