ShiftSee is a marketplace, and marketplaces get healthier when other products can plug in. Today we shipped the foundation for that: a public API, two embeddable widgets, and a developer portal where any builder can register an integration.
What you can build
If you make bookkeeping software, you can now subscribe to a webhook that fires every time a shift completes. Push that into your invoicing engine and your ShiftSee customers stop double-entering hours.
If you run a job board, you can drop our Connect button onto your listings. A visitor signs in (or signs up) on ShiftSee, authorizes your site, and you get permissioned access to their connected businesses or shifter profile.
If you run an industry-specific scheduling tool, you can post shifts into the ShiftSee marketplace directly from your UI using the Schedule widget. Your users keep working in your interface, and the shifts reach ShiftSee's pool of connected workers.
How it works
Two authentication flows: API keys for server-to-server calls (you set an x-api-key header on every request), and OAuth 2.0 with PKCE for user-permissioned access (your users explicitly grant you access to their account).
Webhooks ship with HMAC-SHA256 signatures, the same pattern Stripe uses. We send a t=<unix>,v1=<hex> header on every delivery. Verify the signature in your webhook handler and you can trust the payload without a round-trip to us.
Rate limits start at 1000 requests per hour per partner, with the standard X-RateLimit-* response headers so your client knows when to back off.
Where to start
Visit /developers to register an app and mint your first API key. The portal walks you through the OAuth flow and lets you configure webhook endpoints. The full reference is in the same place.
If you build something interesting, email us. We will feature it.