Developer contract

A narrow, auditable API for work-time evidence

Integrate Regsta through a versioned OpenAPI contract, tenant-scoped credentials, stable errors, employee and shift resources, domain events, and signed webhooks.

GET /api/v1/openapi
GET /api/v1/employees
GET /api/v1/shifts

Contract

Versioned and machine-readable

Public endpoints live below /api/v1 and the OpenAPI document is available to validate clients automatically. Breaking contracts require a new version.

Scope

One credential, one company

API keys belong to one tenant and carry explicit scopes. Integrations never need employee passwords or service-role credentials.

Trace

Stable errors and request IDs

Machine-readable error codes and request identifiers connect client failures to operational logs without exposing internal details.

Events

Domain facts, not internal tables

Employee, shift, export, and settings events form the stable integration vocabulary for reporting, delivery, and future jobs.

Delivery

Signed outbound webhooks

Administrators select exact event types and a public HTTPS receiver. Payloads are HMAC-signed, replay-resistant, retried with bounded delivery semantics, and isolated per tenant.

Company administrators issue and revoke integration credentials inside Regsta. Questions about scopes or rollout can be sent to hej@regsta.com.