ATAPI Twin
Pages

Operate

Keys, privacy, and SSO

Who can call a twin, and who can sign in.

A public twin answers /sim/{slug} without a key. Mark it private on the create step, or later in settings, and callers must send Authorization: Bearer at_live_... or x-api-key. Keys are created on the Keys page, shown once, and can be revoked.

Developer and above can call https://{slug}.apitwin.dev/... as well as /sim/{slug}. The hostname is the slug. Free workspaces stay on the /sim path.

On Developer, a miss can be forwarded to a local process at ws://localhost:3001/tunnel/{slug}?key=at_live_.... That tunnel is the local hub, not a public ingress.

On Team, a twin can require a verified client certificate. The check looks at cf-client-cert-verified, x-ssl-client-verify, or a forwarded client certificate header. An owner on Team can save OIDC for one email domain. Sign-in starts at /sso with a work email. The password form stays on /login. People who sign in that way join the workspace as viewers.

SAML is Enterprise only. It posts back to /auth/saml/acs. Those accounts also join as viewers. There is no mock SAML identity provider. Self-hosting is listed on Enterprise and arranged with us. The app does not ship an installer.