Summary and recommendation
Yardi does not maintain a public developer portal, and no REST API for user management is documented in any publicly accessible resource.
SCIM 2.0 support exists in the context of Voyager (Enterprise tier), but the endpoint URL is provisioned per-customer by Yardi - no generic base URL is published.
Configuration requires direct engagement with the Yardi support or account team;
this is not a self-serve integration path.
Breeze and Voyager are architecturally separate platforms and should not be assumed to share integration capabilities.
API quick reference
| Has user API | No |
| SCIM available | Yes |
| SCIM plan required | Enterprise (Voyager) |
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 has been found in official Yardi documentation.
Alternative event strategy: Yardi integrations are typically handled through approved partner agreements via the Yardi Marketplace; polling or file-based data exchange (e.g., RENTCafé Connect) may be available to approved partners.
SCIM API status
- SCIM available: Yes
- SCIM version: 2.0
- Plan required: Enterprise (Voyager)
- Endpoint: Not documented
Limitations:
- No public SCIM endpoint URL is documented; endpoint is provisioned per-customer by Yardi.
- SCIM support is referenced in third-party IdP integration contexts but Yardi has not published official SCIM developer documentation publicly.
- Configuration requires direct engagement with Yardi support or account team.
- SSO prerequisite status is unconfirmed from official sources.
- Supported SCIM operations (e.g., Create, Update, Deactivate) are not enumerated in any publicly available Yardi documentation.
Common scenarios
The only documented integration surface for identity workflows is SCIM 2.0 on Voyager Enterprise, surfaced in third-party IdP integration contexts such as Okta or Azure AD connector configurations.
Supported SCIM operations - Create, Update, Deactivate - are not enumerated in any official Yardi documentation, so operation coverage must be validated during the provisioning engagement with Yardi.
Any identity graph built on top of Yardi must account for the fact that user object fields, attribute mappings, and supported filters are undocumented publicly and will vary by tenant configuration.
The Yardi Marketplace describes integrations primarily scoped to property data - leases, payments, maintenance - and should not be conflated with user or identity management surfaces.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core risk is assuming SCIM availability implies a standard, self-configurable integration: Yardi's SCIM endpoint is tenant-specific, undocumented publicly, and gated behind a partner or customer contract. Teams that begin building an identity graph against Yardi without first completing the Yardi-side provisioning engagement will hit a hard blocker with no public workaround.
Webhooks for user-management events are not documented; polling or file-based exchange via RENTCafé Connect may be available to approved partners, but this is not a substitute for event-driven provisioning.
API access of any kind - SCIM or otherwise - requires an approved Yardi partner agreement or direct contract, making this a non-starter for teams that have not yet confirmed their integration entitlement with Yardi directly.
Automate Yardi 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.