Summary and recommendation
HighRadius does not publish a user-management or provisioning REST API.
The developer portal at developer.highradius.com is scoped to ERP connectors and financial data APIs - AR, AP, and treasury workflows - with no documented endpoints for user CRUD operations.
No SCIM 2.0 endpoint, no webhook system for user lifecycle events, and no publicly documented auth scopes for identity operations were found as of this research pass.
Any identity graph synchronization against HighRadius would require a direct enterprise agreement and professional services engagement, not a standard API integration.
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 lifecycle events found in official HighRadius documentation.
Alternative event strategy: User administration is performed through the HighRadius UI or via SAML SSO configuration; no programmatic user-management webhook is documented.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Limitations:
- No publicly documented SCIM 2.0 endpoint found in official HighRadius developer or help center documentation.
- IdP integrations (Okta, Entra ID, etc.) are not listed as supported in official docs as of research date.
Common scenarios
No supported API scenarios for user provisioning or deprovisioning were identified in official HighRadius documentation.
User administration appears to be handled exclusively through the HighRadius admin UI or SAML-based SSO configuration.
Teams attempting to build automated joiner-mover-leaver workflows against HighRadius via API should treat this as an unsupported path until HighRadius explicitly documents provisioning endpoints or confirms SCIM support through their enterprise channel.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The most common integration trap with HighRadius is assuming that because the platform exposes financial data APIs, user-management APIs exist in parallel - they do not. The developer portal's API surface is entirely finance-domain: ERP connectors, invoice data, payment workflows.
There is no documented auth method, no rate limit specification, and no pagination contract for any user-scoped resource, because no such resource is publicly available.
Any integration beyond financial data APIs - including attempts to sync HighRadius accounts into an identity graph - requires a custom enterprise agreement and carries no guarantee of a programmatic interface.
Automate HighRadius 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.
