Summary and recommendation
Reachdesk does not publish a developer documentation portal, and no public REST API for user management has been identified.
SCIM 2.0 support is referenced in third-party directories, but no official Reachdesk help article confirms the endpoint URL, supported SCIM operations (Create, Update, Deactivate, List), or the specific plan tier required to enable it.
Auth method - whether API key, OAuth 2.0, or bearer token - is undocumented publicly;
do not assume a mechanism without direct vendor confirmation.
All integration details must be sourced from Reachdesk sales or support before any provisioning pipeline is designed.
API quick reference
| Has user API | No |
| SCIM available | Yes |
| SCIM plan required | Contact Sales (pricing context suggests enterprise-tier engagement; specific plan gate not publicly documented) |
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 was found in official Reachdesk documentation.
Alternative event strategy: Contact Reachdesk sales/support for integration options.
SCIM API status
- SCIM available: Yes
- SCIM version: 2.0
- Plan required: Contact Sales (pricing context suggests enterprise-tier engagement; specific plan gate not publicly documented)
- Endpoint: Not documented
Limitations:
- No publicly documented SCIM endpoint URL or configuration guide found in official help center.
- No confirmed IdP-specific connector documentation (Okta, Entra, Google Workspace, OneLogin) found.
- SCIM availability is indicated by third-party SCIM directory references only; official Reachdesk docs do not publicly confirm supported operations or limitations.
Common scenarios
In an identity graph, Reachdesk would sit as a downstream leaf node receiving provisioning events from your IdP - Okta, Entra ID, Google Workspace, or OneLogin - via SCIM.
However, IdP-specific connector documentation has not been found in official Reachdesk sources, and the SCIM endpoint itself is unconfirmed.
Until endpoint and supported-operation details are confirmed by the vendor, Reachdesk cannot be reliably modeled as an active node in an automated identity graph.
A platform like Stitchflow's MCP server with 60+ deep IT/identity integrations can surface Reachdesk access state from adjacent systems even when the app itself lacks a queryable API.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core risk is building a provisioning dependency on SCIM availability that has not been officially confirmed. Seat counts and send limits are contract-gated, meaning provisioning behavior may vary by agreement - a SCIM Create that succeeds in one customer's environment may fail or behave differently in another's.
No rate limit headers, retry-after signals, or pagination behavior has been documented, so any sync loop built without vendor-confirmed specs is operating blind. Webhooks for user-management events are also absent from public documentation, eliminating event-driven deprovisioning as an option without a polling workaround.
Automate Reachdesk 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.
