Summary and recommendation
Murex MX.3 does not expose a publicly documented REST API for user management.
No SCIM 2.0 endpoints, no IdP connectors (Okta, Entra ID, Google Workspace, OneLogin), and no webhook system for user-lifecycle events have been confirmed in any public Murex documentation.
All integration capabilities are delivered under enterprise contracts via professional services or certified implementation partners.
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 Murex documentation.
Alternative event strategy: Murex MX.3 is an on-premise/private-cloud enterprise capital markets platform. User provisioning and access management are typically handled via internal LDAP/Active Directory integration or manual administration within the MX.3 GUI, not via a public REST API.
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 Murex documentation.
- Murex MX.3 is a closed enterprise platform; integrations are typically delivered via professional services engagements.
- No IdP connectors (Okta, Entra ID, Google Workspace, OneLogin) are publicly listed by Murex.
Common scenarios
No automatable provisioning scenarios can be documented with confidence.
User provisioning in MX.3 is typically handled through internal LDAP/Active Directory integration or manual administration within the MX.3 GUI.
Any identity graph construction that includes Murex mapping users, roles, and entitlements across your environment
will require data sourced directly from your internal directory or extracted via a Murex professional services engagement, not via a public API call.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
Do not assume generic SCIM or REST endpoints exist for MX.3 - none have been confirmed in public documentation, and attempting to reverse-engineer undocumented endpoints in a capital-markets platform carries significant compliance and contractual risk. The Murex developer and community portal is access-gated, so no community-validated workarounds are available for public review.
Any integration scoping should begin with Murex support or a certified partner before any technical implementation is attempted.
Automate Murex 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.
