Create a sign-in token for a collaborator
Mints a short-lived, single-use sign-in token for a collaborator in the account, so you can drop that collaborator straight into their Juicer dashboard without showing the login screen — for example, when embedding the dashboard in an iframe on your own site.
The returned sign_in_url signs the user in and redirects to their
dashboard. It is built against your account’s white-label host when one
is configured, so it works as an iframe src on your site. The token
expires in 30 minutes and can only be used once.
Pass an optional feed_id to land the user directly on that feed’s
editor instead of the dashboard home — useful right after creating a
feed for the collaborator. The feed must be one the collaborator is
assigned to, otherwise the call returns 404.
Requires an account owner or manager API key. The target user must be a
collaborator in the current account; minting a token for an owner or
manager returns 422.
This endpoint is only available when sign-in tokens are enabled for your
account; otherwise it returns 403.
Token reuse is keyed on the destination. If the collaborator already
has an unconsumed token for the same destination, you normally get that
same token back rather than a new one; concurrent calls for the same
destination may still mint separate tokens. The dashboard home and a
specific feed_id are different destinations, so a request for each one
returns a different token.
Expiry alone does not retire a token. A token that has expired but was
never opened is revived rather than replaced: the next call returns that
same token with a fresh 30-minute window. A token that is still valid is
returned unchanged, so its expires_at is the time left on the original
window rather than a fresh 30 minutes. A genuinely new token is minted
only once the previous one has been consumed.
Generate the token server-side at page-load time. Never persist it, share it between users, or write it to logs. For its 30-minute window the URL grants immediate access to the collaborator’s dashboard.
Authorizations
API key prefixed with jcr_. To obtain a key programmatically
(no dashboard required), see POST /v1/authorize.
Path Parameters
Body
Optional. When provided, the sign-in URL lands the user on this feed's editor instead of the dashboard home. Must be a feed the collaborator is assigned to.
Response
Sign-in token created