Skip to content

Integrations and API: webhooks, calendar subscriptions and notifications

Connect biik to your own software with the REST API and webhooks, subscribe calendar apps to leave and shifts, and send events to a Slack or Microsoft Teams channel as notifications. On the Professional and Enterprise plans.

What is included

  • See what it reads first

    Before it is set up, every connection lists the events and data it will read. The person installing it can only grant what they can see themselves; removing the connection closes its key and address at once.

  • API and webhooks

    Read and write employee, organisation, leave and shift data with an API key limited to the scopes you choose; the events you pick arrive at your address as signed webhooks. The documentation is on the Developers page.

  • Calendar subscription

    Employees subscribe their calendar app to their own leave and shifts, managers to their team's leave, everyone to the company calendar, through an address. A hidden leave type shows only as “On leave”.

biik Settings › Integrations screen: the connection catalogue, with sample data
biik Settings › API screen: API keys and webhooks, with sample data

Screens in this module

  • Integrations

    The connection catalogue, setup and permission screen, each connection's status and removal. Found under Settings.

  • API and webhooks

    API keys (shown once; with scope, expiry and allowed IP ranges), webhook addresses and the delivery log.

Connections and where they stand today

Each card says what works today. Those that need no account are set up right away.

  • Webhook

    No account needed. The events you choose go to your address as signed requests; the delivery log shows each one.

  • API app

    No account needed. You name an app and open a key whose role, scopes and expiry you limit.

  • Slack and Microsoft Teams

    Sends notifications through your channel's incoming webhook address: the event title and a link to the screen in the app. Approvals and rejections are not given in the chat; they are given in the app.

  • Zapier and Make

    There is no ready-made store connector. A guide explains how to set it up with a generic webhook and an API key.

  • Accounting, bank, MUHSGK and time-clock files

    Accounting entries, the bank payment file and the MUHSGK XML come out of payroll as files; time-clock device records are uploaded as a file.

  • SGK and HBYS

    The SGK service connection point is ready; no provider is connected. The HBYS card appears only in the health pack and reports physician availability to your organisation's own HBYS address as a signed request; no provider is connected for a specific vendor.