This will initiate the Google authentication flow for the current user. A request will result in a redirect to Google's own login browser screen, and upon submit or cancel, will be redirected back the App's registered callback URL (App registration on Timekit is necessary, please get in touch).
Callback URL
If you dont have a callback URL registered in your app settings (or you need to overwrite it), then you can supply the callback as a GET param. Eg. /accounts/google/signup?callback=http://my-api.com/callback
Timekit App header
If you're attempting to visit this URL directly in the browser, you can append a ?Timekit-App=myappname to the URL instead of setting it through the request header
This endpoint can be used both for sign up (of a new Google account not known to Timekit) or as authentication for a known account (based on email address). This also means that multiple Google accounts can be attached to a single user if needed.
Picking calendars to sync
After signing up a new account, calendars belonging to that accounts must be chosen to be synced afterwards. This is done with the [PUT] /calendars/:id endpoint.
Deleting accounts
If you want to disconnect Timekit integration with a Google account, it can be done on this page (logged in with the Google account in question)
Read more about the Google authentication flow here