Summary and recommendation
SketchUp exposes no public REST API for user or subscription management.
The developer APIs (Ruby Extension API, SketchUp C API, LayOut Ruby API) are 3D modeling and geometry surfaces exclusively - they have no user, seat, or identity management endpoints.
User lifecycle operations have no programmatic path via any documented public interface.
User identity is managed through Trimble Identity, a separate Trimble platform.
No public REST API for Trimble Identity user management has been documented as of the policy date.
Any identity graph integration - mapping users across your IdP, HRIS, or access management tooling to SketchUp seats - cannot be built against a native API today.
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 user-management webhooks are publicly documented for SketchUp or Trimble Identity.
Alternative event strategy: Federated SSO via SAML 2.0 through Trimble Identity (Okta, Entra ID supported) is the only documented automated identity integration. Manual seat management is performed in the SketchUp My Account / Trimble Identity admin console.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No SCIM provisioning endpoint is publicly documented by Trimble/SketchUp as of the policy date.
- User provisioning and deprovisioning must be performed manually via the Trimble Identity admin console or through SAML-based SSO without automated lifecycle management.
- Enterprise SSO (SAML) is available but does not include JIT provisioning details in public docs.
Common scenarios
Given the absence of a user management API, SCIM endpoint, and webhooks, the only documented automated identity integration is SAML 2.0 federated SSO through Trimble Identity, with Okta and Microsoft Entra ID confirmed as supported IdPs.
This covers authentication but not provisioning or deprovisioning.
No JIT provisioning details are present in public documentation, meaning SSO login does not automatically create or assign a seat.
Seat assignment remains a manual console operation regardless of SSO configuration.
There are no documented webhook events for user lifecycle changes (seat assigned, member removed, invitation accepted), so event-driven automation pipelines have no native trigger surface to target.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The most common integration assumption to avoid: SketchUp's developer portal and Ruby/C APIs look like an extensibility surface, but they are scoped entirely to 3D model geometry and extension behavior - not identity or access. Attempting to build user lifecycle automation against those APIs will find no relevant endpoints.
Enterprise customers needing programmatic seat management or identity graph synchronization should engage Trimble/SketchUp enterprise sales directly to determine whether a private API or IdP connector exists under an enterprise agreement. Without that, any automation layer must treat SketchUp as a manual-only system and route all provisioning changes through the admin console UI.
Automate SketchUp 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.
