Summary and recommendation
Blender has no user-management API. It is a free, open-source desktop application (GNU GPL) with no SaaS backend, no cloud tenant, and no concept of provisionable user accounts. There is no base URL, no authentication mechanism, no SCIM endpoint, and no webhook infrastructure - because none of these constructs exist in Blender's architecture.
Blender Studio (studio.blender.org) is a separate subscription service but does not expose a public API for user provisioning, deprovisioning, or identity management. No OAuth 2.0, API key, or SCIM v2 interface is documented or available.
API quick reference
| Has user API | No |
| SCIM available | No |
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: Blender is a desktop application distributed under GNU GPL. It has no SaaS backend and therefore no webhook infrastructure for user lifecycle events.
Alternative event strategy: Not documented
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Not documented
- Endpoint: Not documented
Limitations:
- Blender is not a SaaS product and has no identity provider integration, SSO, or SCIM support.
Common scenarios
No API integration scenarios are applicable. Blender cannot be connected to an identity provider, automated provisioning pipeline, or SCIM-compatible directory service in any supported configuration.
If your organization requires automated lifecycle management for a 3D creation tool, evaluate whether an alternative SaaS-based product with a documented user API better fits your requirements. Data on viable API scenarios for Blender is sparse by design - the product architecture does not support them.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The absence of any API surface is the core caveat here. Teams using an MCP server with ~100 deep IT/identity integrations to automate provisioning across their stack will find Blender is a hard stop - there is no endpoint to call, no token to issue, and no event to subscribe to.
Blender Studio's team plan may appear to offer organizational management, but it exposes no programmatic interface. Any assumption that a subscription dashboard implies API access is incorrect. Treat Blender as an endpoint-managed local application and exclude it from any automated identity lifecycle workflows.
Automate Blender 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.
