API & integrations

Fit SimpleAct into your system landscape

Tickets in Jira and ServiceNow, messages in Teams and Slack, issues in GitHub and GitLab, evidence from SharePoint and Google Drive – plus a documented REST API for everything you connect yourself.

Book a demo See the product

Runtime signal escalated

Service chatbot "Lia"

Incident recorded

AI-based application screening

Evidence approval requested

DPIA report

Governance approval blocked

Marketing copy generator

Change register updated

Model update, application screening

SimpleAct

Event routing

Jira

Issues

ServiceNow

Incident & change records

Microsoft Teams

Channel messages

Slack

Channel messages

GitHub

Issues

GitLab

Issues

Integrations

What you can connect

Each integration is enabled per organisation in the settings. Which ones your plan includes is shown on the pricing page.

JiraTickets

Issues for audit playbook items, governance blockers, evidence approvals, runtime signals, changes and CAPA actions.

ServiceNowTickets

Incident and change records are synchronised with SimpleAct.

Microsoft TeamsMessages

Notices for overdue audits, due legal reviews, approvals, escalations and blockers.

SlackMessages

Notices for overdue audits, due legal reviews and blocked governance approvals.

GitHubRepositories

Issues from governance, evidence and runtime signals; link pull requests, commits and releases as evidence.

GitLabRepositories

Issues from governance, evidence and runtime signals; link merge requests and commits as evidence.

Microsoft SharePointEvidence

Document libraries as an evidence source for requirements and AI systems.

Google DriveEvidence

Shared drives and folders as an evidence source for requirements.

MLflowModels

Import registered model versions and training metrics from your tracking server.

SCIM 2.0Identity

User provisioning from Microsoft Entra ID or Okta with a dedicated SCIM token.

For developers

A REST API with clear rules

The same endpoints the app uses – with API keys per application, published limits and one consistent error format.

Authentication: X-API-Key header or Authorization: Bearer. One key per application, permissions granted explicitly.
Base URL: Your organisation domain plus /api/v1. OpenAPI specification at /api/docs-json.
Limits: 1,000 requests per hour per key, 100 per minute per IP and route, 100 kB per request body.
Ingestion: Dedicated endpoints for runtime signals, model registry and release events from your pipelines.
Webhooks: Deliveries signed with HMAC; a target that fails ten times in a row is disabled automatically.

bash

# Fetch your organisation’s AI inventorycurl https://<your-domain>/api/v1/ai-systems \  -H "X-API-Key: sk_live_…"200 OK · application/json

FAQ

Frequently asked questions about API and integrations

Jira and ServiceNow for tickets, Microsoft Teams and Slack for notifications, GitHub and GitLab for issues and code evidence, SharePoint and Google Drive as evidence sources, MLflow for model metadata and SCIM 2.0 for user provisioning. Anything else connects through the REST API.

With an API key in the X-API-Key header or as a bearer token. Every key carries its own permission list and can never hold more rights than the person who created it.

Yes: 1,000 requests per hour per API key and 100 requests per minute per IP address and route, both at once. Request bodies may be at most 100 kB.

Yes. Ingestion endpoints take runtime signals, model registry entries and release events from your pipelines; MLflow can be connected directly.

More questions? We're happy to help. Send email · Get started

Walk through your system landscape with us

We show which integrations fit your environment and how the API gets into your pipelines.

Book a demo See the product

Open-Source Framework

simpleact-integrations-apis

Where governance data actually comes from, and how to connect existing systems without creating a second data protection problem.

View on GitHub