Summary and recommendation
No public user-management REST API has been confirmed for Charles River IMS.
The platform does expose internal REST APIs covering order management, compliance, and portfolio data, but these are documented exclusively within the authenticated client portal at community.crd.com and are not publicly accessible.
SCIM 2.0 is not supported, and no native webhook system for user-management events has been identified in any public source.
User provisioning is handled via enterprise directory integration-Active Directory or LDAP-configured during implementation.
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: No publicly documented webhook system for user-management events found in official Charles River IMS documentation.
Alternative event strategy: Charles River IMS integrates with enterprise identity providers and LDAP/Active Directory for user provisioning; specifics are only available through direct vendor engagement.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Limitations:
- No publicly documented SCIM 2.0 support found in official Charles River IMS documentation.
- Context data confirms has_native_scim: false.
Common scenarios
Because no public user-management API exists, automated provisioning and deprovisioning scenarios that would typically be built against a REST or SCIM endpoint are not viable without direct vendor engagement.
Any identity graph reconciliation-mapping Charles River IMS accounts to canonical user records across your environment-must rely on directory-level data from AD or LDAP rather than API-sourced user objects.
Teams building automated joiner/mover/leaver workflows should confirm with Charles River Development whether any client-facing provisioning API is available under their specific contract tier before designing an integration.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap with Charles River IMS is assuming that because the platform exposes internal REST APIs for investment data, equivalent endpoints exist for user lifecycle management. They do not appear to, based on all publicly accessible sources.
A second trap is treating AD/LDAP sync as a complete solution: directory integration handles provisioning at the infrastructure layer but typically does not surface application-level role assignments or license states back to an identity graph.
Any automation that depends on application-layer user attributes will require a path through the vendor's support or professional services channel, not a self-service API key.
Automate Charles River IMS 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.
