Running the WorkOS API locally
Blog post from WorkOS
@workos/emulate is an open-source local WorkOS API server designed to make authentication integrations testable without live credentials, network access, persistent remote state, or reliance on happy-path production behavior. It can run through Homebrew, npm, Docker, binaries, or in-process JavaScript tooling, accepts a default test API key, and works with any WorkOS SDK by redirecting its base URL to the local server. Declarative seed files create reproducible users, organizations, memberships, roles, SSO connections, machine-to-machine applications, API keys, and fixed IDs, while valid RS256 JWTs, JWKS endpoints, signed webhooks, and AuthKit and SSO flows allow applications to exercise production-like authentication behavior locally. Interactive mode supports browser-based login tests, and emitted event payloads include email-delivered codes such as magic-link, password-reset, and verification values for end-to-end testing without an email provider. Configurable error hooks can simulate validation errors, rate limits, server failures, and temporary outages, enabling teams to test retry handling, token refreshes, organization selection, webhook verification, and other failure paths reliably in CI.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.