Summary and recommendation
Framer's public API is scoped exclusively to CMS operations - collections, items, and publishing. No user, seat, team, or role-management endpoints are exposed. Developers should not expect to build identity graph integrations against Framer's API in its current state; the surface area for IT or identity automation is effectively zero.
SCIM provisioning is undocumented and should be treated as unavailable until Framer publishes official support. SAML SSO (Okta, Entra ID) exists for Enterprise customers but is configured through Framer support, not a developer-accessible endpoint or dashboard toggle.
Webhooks for user or team events are also undocumented. There is no alternative event-notification mechanism for user lifecycle changes.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | Enterprise |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No webhook system for user or team events is documented in official Framer developer or help center documentation.
Alternative event strategy: No documented alternative for user-event notifications.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- SCIM provisioning is not documented in any official Framer source.
- SAML SSO (Okta, Entra) is available for Enterprise customers but requires contacting Framer support directly.
- No self-serve SCIM setup path exists as of research date.
Common scenarios
Given the absence of user management endpoints, the only viable API automation scenarios for Framer are CMS-scoped:
- Programmatic creation, update, or deletion of CMS collection items via the REST API.
- Triggering site publishes after content updates.
- Syncing external content sources into Framer CMS collections.
No scenarios involving user provisioning, role assignment, seat management, or access revocation are achievable through the API. Any identity graph that includes Framer as a node must rely entirely on manual admin actions or future SCIM support if and when Framer documents it.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap is assuming that SAML SSO implies SCIM. Framer supports SAML for Enterprise, but SSO alone does not automate provisioning or deprovisioning - it only controls authentication. Without SCIM, a user terminated in the IdP retains their Framer workspace seat until an admin manually removes them.
A second trap is the API scope mismatch. Framer's developer documentation is well-maintained for CMS use cases, which can create a false impression of API maturity. The CMS API and the identity/team management surface are entirely separate concerns, and the latter does not exist.
Any tooling - including an MCP server with 60+ deep IT/identity integrations - that attempts to automate Framer user lifecycle management will find no supported endpoints to call.
Automate Framer workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
