Integration Overview

This section documents how external scheduling providers can integrate with Seamlr to enable seamless workforce staffing.

Architecture

flowchart LR
    subgraph Provider["Scheduling Provider"]
        P1[Shift Management]
        P2[Time Tracking]
        P3[Payroll]
    end

    subgraph Seamlr["Seamlr"]
        S1[Candidate Pool]
        S2[Matching]
        S3[Booking]
        S4[Communication]
    end

    Provider -->|Webhook| Seamlr
    Seamlr -->|REST API| Provider

Data Ownership

Note

Understanding data ownership is crucial for a successful integration.

Data Type	Source of Truth	Sync Direction
Shift times, location	Provider	Provider → Seamlr
Number of positions	Provider	Provider → Seamlr
Candidate assignments	Seamlr	Seamlr → Provider
Candidate profiles	Seamlr	Seamlr → Provider
Booking status	Seamlr	Seamlr → Provider

Integration Model

The integration follows an event-driven webhook pattern:

1. Provider → Seamlr: Webhooks notify Seamlr of shift changes
2. Seamlr → Provider: REST API calls to fetch details and sync assignments

All operations are initiated by Seamlr. The provider does not poll Seamlr.

Required Capabilities

Your scheduling system needs to:

1. Send webhooks when shifts are created, updated, or deleted
2. Expose REST endpoints for Seamlr to:
   • Fetch shift details
   • Search and create candidates
   • Assign/unassign candidates to shifts
3. Handle authentication via Bearer tokens
4. Support multi-tenant routing via provider IDs