Integration availability and compatibility
Some documented features have constraints that affect integration. Verify the target hosted environment with a test account before depending on them; the API reference is not a live deployment certification.
For a first test without an app, start with the manual hosted-login walkthrough. The advanced features below are separate work. If the exact endpoint you need is affected, confirm support for that feature before making it part of your app's required sign-in flow.
| Area | Limitation and next step |
|---|---|
| Initial plan activation | A new account can receive an access/subscription error before activating a free plan. Contact support to resolve account provisioning. |
| Application security | Standalone MFA, passkey, magic-link, session, anomaly, logout and JWT-to-session requests can be rejected with 401 despite using the expected application credential. Confirm availability before enabling a required sign-in factor. |
| SCIM and SAML | Protocol requests can encounter the same authentication rejection. Test the full IdP/SP flow and confirm hosted support before rollout. Do not add developer credentials to a protocol request as a workaround. |
| Server-side PKCE initialization | The initializer can encounter authentication rejection. The hosted OAuth guide generates S256 PKCE in your application instead. |
| OAuth password grant | Not supported by the token endpoint, even if a generated client configuration lists it. Use authorization code with PKCE or client credentials as appropriate. |
| JSON signup | Requires a separately provisioned registration key. Quick Build's workspace token does not substitute for it. Hosted signup is a separate flow. |
| Quick Build templates | Review placeholder rendering and generated configuration before use. Ordinary email templates require double braces. |
| SCIM media type and locations | Write requests currently require application/json. A returned meta.location may omit /e/v1; use the documented resource base and check identity-provider compatibility. |
| SCIM capabilities | No password provisioning, bulk operations, sorting, ETags or arbitrary custom-schema persistence. |
| SAML logout | No SAML Single Logout endpoint is provided. |
| Application profile deletion | Self-service profile DELETE is limited to designated test-account patterns. It is not a general end-user account-deletion flow. |
For an affected endpoint, capture the method/path, HTTP status, sanitized body and time, then contact support. These constraints do not call for private service credentials or changes to infrastructure under your control.