API & Integrations: Connecting SCREENish to Your Other Tools

API & Integrations in the left menu is where SCREENish meets the rest of your stack. From that one page you can send alerts into a chat channel, push tracked time into Jira, ClickUp or Trello, subscribe a calendar or a spreadsheet to a live feed, download a timesheet for your accountant, and issue API keys for your own software. Everything is created there, and everything can be revoked there.

Before the first connection: the API access terms

The first time you open the page SCREENish shows the API access terms. Tick the box and press Accept. The acceptance is recorded with the version, the moment and who accepted it on behalf of the organisation, and until it is given no key, connection or feed link can be created. The text stays available afterwards from the Show the text link under the heading.

The five routes out

Chat alerts. A readable message in Slack, Microsoft Teams, Discord or Google Chat when someone starts or stops tracking, when an activity review opens, or as a daily summary. See Slack: Getting SCREENish Alerts in a Channel.
Time push. Approved time lands as a Jira worklog, a ClickUp time entry or a Trello comment, once an hour, per member and day.
Feeds. A private link your calendar or spreadsheet refreshes on its own: calendar events or a live timesheet.
Accounting exports. A CSV timesheet for a period, ready for QuickBooks Time or a payroll import. See QuickBooks Time and Payroll: Exporting Timesheets.
API and webhooks. An API key for your own software, and signed webhooks for Zapier, Make and n8n or anything you write yourself.

What leaves SCREENish, and what never does

Every route above carries the same narrow set: hours, activity counts, member and project names, and verdicts — an activity review was opened, a face check passed or failed. None of them carries screenshots, application names, window titles, biometric data or pay rates. That is clause 3.5 of the Data Processing Agreement, and no key, connection or feed link can widen it. A destination you configure is your recipient: once a message reaches your Slack workspace or your Jira site, what happens to it is governed by your agreement with that provider.

Who can set it up, and what is recorded

The page needs an active subscription. Delegated managers who reach the dashboard see the same page and the same buttons.
Recent activity at the bottom lists every change — a key created or revoked, a connection added, paused or removed, a feed link issued, terms accepted — with the time and who did it.
Keys, connections and feed links live with the account. Closing the account erases the stored credentials.

Secrets are shown once

An API key, a webhook signing secret and a feed link are each displayed once, in a yellow box at the moment they are created. Copy them then. If one is lost, revoke it and create another — SCREENish cannot show it again.

The technical description of every endpoint, parameter and header lives on the developers page.