What determines availability
Tikk applies these layers in order:1
Weekly schedule
Your weekly schedule is the base. Set the hours you’re open for each day of the week (say, Mon-Fri 09:00-17:00). Slots outside those windows never show.
2
Date overrides
Adjust or block availability on specific dates. Use these for holidays, vacation or one-off changes to your hours.
3
Synced calendars
Tikk checks every connected calendar. If any calendar has a busy event overlapping a slot, the slot is hidden. No double bookings.
4
Buffer times
Buffers add a gap before or after each booking. With a 15-minute buffer after, a meeting ending at 10:00 pushes the next slot to 10:15.
5
Service-specific settings
Each service can override the base window and set its own lead time (like “at least 24 hours notice”). These narrow the pool further.
How slots are generated
Tikk splits your open windows into slots of the service’s duration (default 30 minutes). A slot only makes the response if it passes every layer. One conflict, one drop.Slots are generated in real time when you hit the availability endpoint. Results always reflect your latest calendar state.
Slot fields
Each slot returns:start and end are always UTC so you can do reliable time math. Use label when you want a ready-to-show string in the host’s local time.
Timezone handling
Your weekly schedule and date overrides live in your timezone, set in account settings. Each returned slot includes alabel in your timezone. Bookers see times auto-converted to their local timezone.
General vs service-scoped availability
You can query in two modes:- General availability
- Service-scoped availability
Without a
service parameter you get your overall open windows from the base schedule. Useful for a broad calendar view or checking whether you’re free on a given day.Full request and response shape lives in the List Availability reference.