Redirect the user to begin JumpCloud sign-in. Use this when the user clicks sign in. You'll need JumpCloud configured for your partner. The user is sent through JumpCloud and returned signed in: JumpCloud sends them back to JumpCloud: callback, and the dashboard then redeems the one-time code with JumpCloud: exchange the code. Open this URL in the browser (a link or a full-page navigation), not with fetch or XHR: the response is a redirect, and the sign-in state is kept in a session cookie. Check which sign-in methods an email can use returns this URL as sso_url.

Prerequisites: none. The user must have JumpCloud sign-in turned on; that's checked at the callback.

Authentication: Public (no token). Nobody is identified at this step; who can sign in is checked at the callback (users with JumpCloud sign-in turned on, whose company is a partner, an account or a location).

Rate limit: 10 requests per minute, counted per client IP address.