Table of contents:
Resources can have calendars, one or multiple, that contains events and bookings. If you're a two-sided marketplace, you can also create resources for your consumers/end-users to make mutual availability checks, but it's not required.
Onboarding & resource creation
Timekit can be used without your users even knowing about us, as user/resource creation and provisioning can be done 100% through the API. In the onboarding flow in your app, you can simply add an API call to Timekit where you create the resource (with the email, password, timezone etc. provided through your own screens) and save the resulting API token - more on that below.
With Google connect, the user would however have to accept OAuth permissions manually, but you can control the callback redirect so users are led back to your own app instead of Timekit.
User API tokens (credentials)
Whenever you create a new user/resource (plain user or Google connected), you will receive an API token in the response. We recommend you save this API token in your own database, on your user/resource model, as you will have to use the token for authentication to the Timekit API for all subsequent requests.
Connect Google account to create user
After the callback, save the "email" and "token" query params for the next API requests
Sync user's Google calendars to Timekit
Get user's calendars
The calendar IDs can be used as targets for creating events/bookings
Specify which calendars to sync for availability
Perform a sync
If you're planning to use Booking.js, our UI widget, you'll also need to generate a special API token that can be used publicly client-side. These credentials are locked down for only widget relevant endpoints.
This is done by calling:
Continue to the next guide and learn how to create and update bookings