An Appointment Scheduling API and Integrations.
and what it doesn't.
This page is deliberately not a wall of logos. It shows four things separately: what you have on day one, what there is a documented interface for, what we switch on individually for your business — and what is not there at the moment.
<iframe src="https://…/widget/your-business"
width="100%" height="720" frameborder="0"></iframe>This is what you have on day one
These three things are included in every plan and need no activation from us.
Booking inside your website
You get a booking page with an address of its own and an embed code for your existing website. Both lead to the same flow. It works anywhere your website or website system can embed an iframe.
The appointment in your clients' calendar
The booking confirmation carries a calendar file (.ics) as an attachment, which can be imported into compatible calendar applications. That is a file format, not a tie-in to a provider.
Emails without your own mail server
Slotara sends the confirmation and the one appointment reminder. You don't have to connect a sending service or set up a domain for sending.
The calendar file is attached to the confirmation, not to the reminder — the reminder is a plain email.
An open interface for the booking flow
If you want to build your booking yourself — in your own website, in an app, or in a system you already have — there is a documented booking API for that. It covers the booking flow: locations, services, free times, free days, creating a booking and cancelling it later through a link.
It also exposes the public booking flow as a documented interface and is designed for a limited number of requests per minute. It is usable on every plan — and it is explicitly not the key-based access covered in the next section.
What it cannot do: it does not reach your internal data. Reports, staff management and settings do not sit on this interface.
Read the technical descriptionWhat exists, but not at the push of a button
For two things there is code that works — and you still cannot get there on your own: access via a key of your own, and outgoing notifications to your system.
Access with a key of your own
Access for your own system, for connections that go beyond the public booking flow. Which areas your key may reach is something we agree together when it is switched on.
A notification to your system
Slotara can notify your system when a booking is created. The notification is signed so your system can verify it came from us, and it is retried several times if delivery fails.
Today exactly one event is provided for: a new booking. There are no further events.
What's not included today
So you know before you sign up, not after:
- No calendar synchronisation
- Slotara does not sync with Google Calendar, Outlook or Apple Calendar. Appointments go out as a calendar file with the confirmation; an ongoing exchange in both directions is not built. There is no calendar feed to subscribe to either.
- No SMS and no WhatsApp
- Reminders and confirmations go out by email only.
- No Zapier, no Make, no WordPress plugin
- There is no ready-made connector to automation services and no plugin for WordPress. Anyone who wants to connect something uses the interface from the section before last.
- No direct connection to accounting software
- Slotara does not currently offer a generally available customer-invoicing feature, and there is no direct handover to DATEV, lexoffice or similar programs. What you get out is a CSV export you can pass on.
- No automatic video call links
- Slotara does not create Zoom, Teams or Meet links for an appointment.
We mark as available only what is actually usable today.
Why this page separates four states
A logo does not tell you whether something works, whether it belongs to your plan, and whether you can switch it on yourself. So this page keeps them apart: what runs right away, what there is a documented interface for, what we switch on individually, and what is not there at the moment. We mark as available only what is actually usable today.
Where your data is held
Servers in Germany
The Slotara application runs on servers in Germany.
DPA under Art. 28 GDPR
The data processing agreement applies automatically from the start of the contract.
TLS encryption
Booking page, widget and app are delivered over TLS-encrypted connections.
Frequently asked questions about integrations
Yes, with an embed code — on every plan. Alternatively you share the link to your booking page.
No. Your clients get the appointment as a calendar file with the confirmation and can import it. An ongoing exchange between Slotara and a calendar service is not built.
Yes, for the booking flow: locations, services, free times, creating a booking and cancelling it again. It is documented and usable on every plan. For access beyond that there is API key access — that belongs to the Max plan and is switched on individually on top.
In principle yes: Slotara can notify your system when a booking is created. It belongs to the Max plan and is, beyond that, activated per business — upgrading your plan alone is not enough. Exactly this one event is provided for at the moment.
No, by email only.
Through a CSV export that you download and pass on yourself. There is no direct connection to accounting programs.