URL busy events
This App is for teams that run a small API on their side. Timelish calls your URL and asks, in effect, “When is busy?” Your server answers with busy intervals so Timelish can hide those times from booking. Start and end times are sent as query parameters in a standard ISO date format.
Adding the App
- Agree with your developer or vendor on the exact URL and response format Timelish expects.
- Open Apps, then Store, and install URL busy events.
- Enter the URL. Add optional headers (for example an API key) if your server needs them.
- Save and confirm the App connects. Fix format or auth errors with your technical contact.
If Timelish cannot read the response, see Apps troubleshooting and check server logs on your side.
Good to know
This is not a normal “paste an ICS link” setup. If you only have a calendar link, use ICS Feed instead.
Usage
Keep Timelish in sync with another scheduling system
Use this when: Another product already knows when people are busy and can expose that over HTTP.
You need: A stable HTTPS endpoint, correct response shape, and someone who can fix outages quickly.
Send a secret token with each request
Use this when: Your endpoint must reject anonymous callers.
You need: Headers filled in safely; treat values like passwords.
Removing the App
- Open Apps, then Installed apps.
- Open URL busy events and delete the URL / headers or disconnect the App.
What changes afterward
Timelish stops calling your server for busy times. Availability falls back to your other rules (weekly schedule, calendar Apps, manual busy blocks).
Outside Timelish
Rotate or revoke any API keys you gave Timelish. Your server stays under your control.