Summary and recommendation
Cleverbridge exposes a public API at developer.cleverbridge.com focused exclusively on e-commerce operations: subscriptions, orders, customers, and license keys.
No user-management, workforce provisioning, or SCIM endpoints are documented.
Auth method, rate limit headers, and pagination details are not publicly specified in available documentation.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | N/A |
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: Cleverbridge does support event notifications (e.g., order and subscription lifecycle events) via its platform, but no publicly documented webhook system for user-management events was found in official docs.
Alternative event strategy: Cleverbridge provides order/subscription event callbacks configurable in the merchant back-office, but these are commerce events, not user-provisioning events.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Limitations:
- No SCIM endpoint documented in official Cleverbridge developer or help center documentation.
- No IdP (Okta, Entra, Google Workspace, OneLogin) connector listed by Cleverbridge.
Common scenarios
No viable API scenarios for internal user provisioning or deprovisioning were identified.
The Cleverbridge API's 'customer' object represents end-buyers transacting on the platform - it is not equivalent to an identity-provider user object and should not be mapped to one in an identity graph.
Cleverbridge does support order and subscription lifecycle event callbacks configurable in the merchant back-office, but these are commerce events, not user-provisioning signals and cannot substitute for SCIM or webhook-based identity lifecycle events.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap is conflating Cleverbridge's 'customer' API object with an internal operator or admin identity. These are end-buyer records, not workforce accounts, and attempting to drive IAM decisions from them will produce incorrect identity graph mappings. No OAuth 2.0, SCIM, or user-management endpoints are documented;
generic REST provisioning patterns do not apply. Admin seat management is handled entirely via the merchant back-office UI, with no API surface exposed for that layer.
Automate Cleverbridge 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.
