Summary and recommendation
Roam Research does not publish a public REST API for user or account management.
No documented endpoints exist for creating, listing, updating, or deprovisioning users.
Unofficial community libraries such as roam-js and roam-client interact exclusively with graph data - blocks, pages, and linked references - and provide no surface for identity or lifecycle operations.
Any integration built against these tools cannot be used to manage user accounts and should not be treated as a supported provisioning path.
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 webhook system is publicly documented by Roam Research.
Alternative event strategy: Not documented
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Limitations:
- No SCIM support documented. Roam Research is primarily an individual/research-focused tool with no enterprise identity-management tier publicly available.
Common scenarios
No automation scenarios for user provisioning or deprovisioning are possible against Roam Research today.
The tool exposes no SCIM endpoint, no IdP connector (Okta, Entra ID, Google Workspace, OneLogin), and no webhook system for account lifecycle events.
For teams building an identity graph that maps users to their application access, Roam Research will appear as a gap
accounts exist only at the individual subscription level and cannot be queried, created, or revoked programmatically.
Data is sparse because no such API surface is documented.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The absence of a user management API creates a compounding problem for identity graph completeness. Because each Roam Research subscription is independently owned by the end user, there is no authoritative source an IdP or IGA platform can poll to confirm who has active access.
Offboarding a departing employee does not automatically terminate their Roam subscription or revoke shared graph access - both require manual action by the individual or the graph owner, with no documented confirmation state.
Teams that rely on automated joiner-mover-leaver workflows should flag Roam Research as a tool that will require a manual exception process indefinitely, absent a future enterprise tier with API-based identity management.
Automate Roam Research 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.
