# Oktavia Connect Summary

Canonical URL: https://oktavia.app/developers/connect

## Purpose

Oktavia Connect is the integration layer for external systems that need to send operational data into Oktavia or consume validated labor data from Oktavia.

## External Systems

Oktavia Connect can be used by:

- POS systems,
- payroll tools,
- labor advisory platforms,
- BI systems,
- reservation systems,
- internal customer systems.

## Inbound Data Examples

External systems can send:

- POS daily closes,
- interval sales,
- product summaries,
- reservation forecasts,
- local operational events,
- demand signals.

## Outbound Data Examples

External systems can consume:

- validated worked hours,
- approved absences,
- labor incidents,
- schedule publication events,
- time record validation events.

## Credential Model

Each Oktavia customer controls production credentials from their account.

Partners can build integrations in sandbox mode, but production access is issued by the customer and scoped to one connection, one environment and selected permissions.

This model avoids a global partner key with broad access to all customers.

## Security Requirements

- Use API keys per connection.
- Sign inbound webhook bodies with HMAC-SHA256.
- Include timestamps.
- Include idempotency keys for retryable events.
- Keep sandbox and production credentials separated.
- Never expose secrets in a browser or public client.

## Developer Resources

- Developer portal: https://oktavia.app/developers/connect
- Markdown guide: https://oktavia.app/developers/oktavia-connect.md
- Public status: https://oktavia.app/status