Signal API
Redirect login links as MarkdownUse a clean Markdown version of this page with an agent or local tooling.

Redirect login links

Send an embedded identity into hosted Signal with a short-lived, one-time URL.

Redirect login links open the hosted Signal application in a top-level browser navigation. They are separate from iframe embed sessions and cannot be used as embed-session tokens.
Hosted rolesThe identity’s grant controls authorization after sign-in. viewer is read-only, editor manages supported operational features, and admin additionally manages settings and partner-managed users within the granted project or location. A login link authenticates the identity and never elevates its role.
Server-side onlyCreate, inspect, and revoke login links from your backend with a Signal API key. Never expose an API key in browser code, logs, or a public URL. Treat each returned login URL as a temporary credential.
Managed identity accountThe supplied external_user_id resolves an embedded identity in the API key’s workspace. On first use, Signal provisions a dedicated partner-managed hosted profile for that workspace and external identifier. It has no password and never matches, links, or signs into an existing Ceyo account by email.
Access and destination checksThe API key needs login_links:manage, and the requested project or location package must enable Customer access through pricing.frontend_delivery_enabled. This single entitlement enables both hosted Signal UI and redirect login links. Signal verifies the package entitlement and embedded access both when the link is created and when it is used. Return URLs must use an exact HTTPS origin in the API key’s allowed_origins; redirect paths stay within hosted Signal.