SIsixminute
calendar

Start a connect: store the window's state, answer the provider's consent page

The window made the state and the PKCE verifier and keeps them; this seals the state, the caller and the S256 challenge into state_token, good for ten minutes, which the window keeps and hands back with the finish, and answers the consent page with the hosted redirect page of this deploy's page as redirect_uri. The state is also stored for ten minutes, for a page that finishes without the token. 409 while the caller has a connected account.

post/v1/calendar/connect

Request

  • Base URL
    https://api.sixminute.ai (the document declares no server; this is the origin it was published from)
  • Auth
    HTTP bearer

Request body

provider'microsoft' | 'google' required
statestring required
code_challengestring required

Response

The consent page.

authorize_urlstring uri required
state_tokenstring

Changes

No recorded changes to this operation across all 2 revisions of this API.