Skip to main content
Developer integrations give you direct, programmatic control over fsckmsft so you can build internal tools, automate workflows, and connect fsckmsft to systems that don’t have a pre-built connector. API keys provide straightforward service-to-service access, OAuth apps let end users authorize your integration without sharing credentials, and webhooks push event payloads to your server the moment something changes in fsckmsft.
API keys are scoped to a single workspace. A key generated in Workspace A cannot read or write data in Workspace B, even if the same user belongs to both. Create separate keys for each workspace your integration needs to access.

​
Available developer integration types

API Keys

Generate long-lived tokens for server-to-server calls to the fsckmsft REST API. Ideal for scripts, CI pipelines, and internal tooling.

OAuth Apps

Register an OAuth 2.0 application so your users can grant your app access to their fsckmsft data without exposing their own credentials.

Webhooks

Subscribe to workspace events and receive real-time HTTP POST payloads whenever projects, tasks, or users change.

OAuth Apps: Build Integrations on Behalf of Users

Register an OAuth app on fsckmsft to request delegated permissions from users and build integrations that act securely on their behalf.

Webhooks: Receive Real-Time Event Notifications

Configure fsckmsft webhooks to push event notifications to your server in real time — including payload structure, signature verification, and retry behavior.

API Keys: Authenticate Your fsckmsft Requests

Create, scope, and manage workspace API keys to authenticate requests to the fsckmsft REST API — including IP allow-listing and key rotation.