Ssoready

SSOReady exposes a REST API for managing organizations, SAML connections, and SCIM directories. Endpoints cover organization CRUD, SSO connection configuration (entity ID, cert, ACS URL), and SCIM directory management. Authentication is via API key (bearer token). The API follows RESTful conventions with JSON request/response. SDK support for Python, TypeScript, and Go is documented. The surface is well-designed for programmatic B2B onboarding flows.

Standard HTTP status codes with JSON error bodies. Validation errors return 400 with field-level detail. Auth failures return 401. The service is designed for low-frequency management operations (SSO config changes) rather than high-throughput API calls. Error documentation is functional. Rate limits are not prominently documented. SAML assertion processing errors are surfaced as events rather than API errors.

SSOReady is a newer (2024) open-source SAML and SCIM provider designed for B2B SaaS teams. It handles enterprise SSO (SAML 2.0) and directory sync (SCIM 2.0) with a REST API for managing organizations, SSO connections, and SCIM directories. Agents can programmatically configure SSO for enterprise customers, manage user provisioning, and handle SAML assertion callbacks. A managed cloud offering is available alongside self-hosting. Being newer, the product is actively developed but less battle-tested than WorkOS or Auth0 for enterprise SSO. Confidence is docs-derived.

API key authentication for all management API calls. The SAML flow itself is handled by SSOReady's hosted endpoints. No per-resource scoping documented — account-level API keys. SCIM provisioning uses separate SCIM bearer tokens per directory. Self-hosted deployments manage their own key storage. Standard API key security model; appropriate for agent-driven onboarding automation.

Documentation at ssoready.com/docs covers getting started, API reference, and integration guides. The API reference is complete for core endpoints. SDK-specific guides are available. Community support via Discord. As a newer product, documentation is well-structured but has gaps in edge cases. GitHub is actively maintained. Quality is good for the core use case; advanced SCIM provisioning scenarios are less documented.